dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6118

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in AstrBotDevs AstrBot up to 4.22.1. Impacted is the function add_mcp_server of the file astrbot/dashboard/routes/tools.py of the component MCP Endpoint. This manipulation of the argument command causes command injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the add_mcp_server function of AstrBot's dashboard tools endpoint. The function accepts a 'command' argument from user input and passes it unsanitized to system execution, allowing an attacker to inject arbitrary OS commands. The exploit is remotely accessible through the web dashboard.

MitigationImplement strict input validation and sanitization on the 'command' parameter, preferably using allowlist validation or avoiding shell execution entirely by using subprocess with argument lists instead of shell commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AstrBot is installed
    Search for AstrBot installation directories or running processes. Common locations: /opt/astrbot, /home/*/astrbot, or check running Python processes for 'astrbot'. Review project dependencies for astrbot package.
    Affected if AstrBot is present in the environment
  2. Locate the vulnerable add_mcp_server function
    Search the AstrBot source code for the file containing 'add_mcp_server' function, typically in a dashboard or tools module. Inspect the function to verify it accepts a 'command' parameter.
    Affected if The add_mcp_server function exists and processes a 'command' argument
  3. Verify dashboard endpoint exposure
    Check web server configuration or reverse proxy settings to determine if the AstrBot dashboard/tools endpoint is accessible from the network. Look for routes handling /dashboard, /tools, or /mcp paths.
    Affected if The dashboard tools endpoint is reachable over the network without proper access restrictions
  4. Examine command parameter handling
    Review the add_mcp_server function code to see if the 'command' parameter is passed directly to system execution functions (os.system, subprocess with shell=True) without sanitization or validation.
    Affected if The 'command' parameter is executed via shell without input validation
  5. Check for authentication on the dashboard
    Review authentication and authorization configuration for the dashboard endpoint. Determine if unauthenticated or low-privilege users can access the add_mcp_server functionality.
    Affected if The endpoint lacks proper authentication or allows low-privilege users to invoke the function

The environment is affected if AstrBot is installed with the dashboard tools endpoint accessible and the add_mcp_server function passes the 'command' parameter directly to system execution without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on the 'command' parameter, preferably using allowlist validation or avoiding shell execution entirely by using subprocess with argument lists instead of shell commands.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6118 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data