CVE-2026-10211
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 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.
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 path authorization vulnerability exists in the _normalize_rw_path function in astrbot/core/tools/computer_tools/fs.py. The function fails to properly validate or authorize file system paths, likely allowing path traversal or unauthorized file access. This is a remote authorization bypass in a file handling function.
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.
-
Verify AstrBot installation and versionCheck if AstrBot version 4.23.6 is installed. Run: pip show astrbot or check package metadata to get the installed version number.Affected if The installed version is exactly 4.23.6 (the affected version)
-
Locate the vulnerable fileFind the file astrbot/core/tools/computer_tools/fs.py in the AstrBot installation directory. Common paths: site-packages/astrbot/core/tools/computer_tools/fs.py or the project source directory.Affected if The file exists in the AstrBot installation
-
Inspect the _normalize_rw_path functionOpen fs.py and locate the _normalize_rw_path function. Examine whether it uses os.path.realpath() or equivalent canonical path checks to ensure resolved paths stay within allowed directories.Affected if The function exists but lacks proper path validation (no realpath() check or directory boundary enforcement)
-
Check if file operations are enabledDetermine whether the file read/write tool/feature is enabled or accessible in AstrBot configuration. This may be in config files or tool enablement settings.Affected if File read/write operations via computer_tools are enabled and accessible to users
You are affected if AstrBot 4.23.6 is installed, the vulnerable fs.py file exists, and the _normalize_rw_path function lacks proper path validation to prevent path traversal attacks.
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 dataFix the _normalize_rw_path function to properly canonicalize paths and enforce authorization checks before allowing file operations. Validate all paths against intended access controls and prevent traversal beyond permitted directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-10211 — 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-10211 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