# CVE-2026-6117: AstrBotDevs AstrBot install-upload Endpoint plugin.py install_plugin_upload sandbox

> Remote attackers can exploit a sandbox bypass in the plugin upload endpoint to execute arbitrary code within the AstrBot application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-rf4q-qfjf-vw22

## What is CVE-2026-6117?

CVE-2026-6117 is a medium-severity vulnerability in AstrBotDevs AstrBot, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-265, CWE-264

## Which versions are affected by CVE-2026-6117?


## How do I fix CVE-2026-6117?

No fix has been published for CVE-2026-6117 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6117 being exploited?

There is no known exploitation of CVE-2026-6117 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6117 and fix it if it is affected.

What it is: CVE-2026-6117 is a medium-severity vulnerability in AstrBotDevs AstrBot, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6117 in the wild and no public exploit code.

Affected product: AstrBotDevs AstrBot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6117/ (Markdown: https://insights.sbomify.com/CVE-2026-6117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6117
- OSV: https://osv.dev/vulnerability/CVE-2026-6117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6117/
Summaries are generated and may contain mistakes; the official description above is the record.