CVE-2026-6117
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 · uneditedA vulnerability was found in AstrBotDevs AstrBot up to 4.22.1. This issue affects the function install_plugin_upload of the file astrbot/dashboard/routes/plugin.py of the component install-upload Endpoint. The manipulation of the argument File results in sandbox issue. The attack can be executed remotely. The exploit has been made public and could be used. 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 · moderate confidenceA sandbox vulnerability exists in AstrBot's plugin upload endpoint (install_plugin_upload function in astrbot/dashboard/routes/plugin.py). The file upload mechanism improperly handles the File argument, allowing manipulation that bypasses sandbox restrictions. This could enable remote attackers to upload malicious content or access restricted system resources.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AstrBot installationRun 'pip show astrbot' or check if the astrbot package directory exists in your Python environmentAffected if AstrBot is not installed or the package is missing
-
Locate the vulnerable plugin route fileCheck for the file astrbot/dashboard/routes/plugin.py in your AstrBot installation directoryAffected if The file exists and contains the install_plugin_upload function
-
Verify the sandbox handling in the upload functionInspect the install_plugin_upload function for proper sandbox enforcement on the File argument processingAffected if The function lacks or has weak sandbox validation on file uploads
-
Check if plugin upload endpoint is exposedReview your dashboard or web server configuration to determine if the plugin upload route is accessible (typically /plugin/install or similar endpoint)Affected if The upload endpoint is publicly or broadly accessible without additional restrictions
-
Compare installed version to any available patched releasesRun 'pip show astrbot' to get the version and compare against any official CVE references or release notes for patchesAffected if Your installed version predates the patch date or no patch is available yet
You are affected if AstrBot is installed with the plugin upload endpoint accessible and the install_plugin_upload function lacks proper sandbox validation on file arguments.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and sanitization for file uploads, enforce strict sandboxing controls, and validate file content/types before processing. Consider restricting upload functionality until an official patch is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6117 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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