# CVE-2026-10211: AstrBotDevs AstrBot fs.py _normalize_rw_path authorization

> Remote attackers can bypass authorization checks in the file system tool to read or modify files due to incorrect path normalization logic.

- **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:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-c6q5-v72x-3cqq

## What is CVE-2026-10211?

CVE-2026-10211 is a medium-severity missing authorization vulnerability in AstrBotDevs AstrBot, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in AstrBotDevs AstrBot 4.23.6. Affected by this issue is the function _normalize_rw_path of the file astrbot/core/tools/computer_tools/fs.py. This manipulation causes incorrect authorization. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-10211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10211 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10211 is a medium-severity missing authorization vulnerability in AstrBotDevs AstrBot, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10211 exists.

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-10211/ (Markdown: https://insights.sbomify.com/CVE-2026-10211/index.md)
```

## Sources

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

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