CVE-2026-10210
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 4.23.6. Affected by this vulnerability is the function _sanitize_prompt_description of the file astrbot/core/skills/skill_manager.py. The manipulation results in injection. The attack may be performed from remote. The exploit has been made public and could be used. 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 code injection vulnerability exists in AstrBot 4.23.6 within the _sanitize_prompt_description function in astrbot/core/skills/skill_manager.py. The function fails to properly sanitize user-supplied prompt descriptions, allowing remote attackers to inject malicious input that gets processed by the application.
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.
-
Identify AstrBot installation and versionRun command: pip show astrbot or check package manager for installed version. Also check astrbot/__init__.py or pyproject.toml for version number.Affected if Installed version matches 4.23.6 or falls within the affected range around this version
-
Locate the vulnerable fileVerify existence of astrbot/core/skills/skill_manager.py in the installation directory. Use: find /path/to/astrobot -name skill_manager.pyAffected if File exists at astrbot/core/skills/skill_manager.py in the installed version
-
Confirm the vulnerable function existsSearch for '_sanitize_prompt_description' function definition within skill_manager.py using grep or text search.Affected if Function _sanitize_prompt_description is present in the code
-
Determine if prompt description feature is accessibleCheck if skills or prompt description functionality is enabled. Look for skill-related configuration files, admin panels, or API endpoints that accept prompt description input.Affected if User-supplied input can be passed to prompt description fields through web UI, API, or configuration interfaces
-
Review skill management permissionsExamine AstrBot role or permission settings to see which users can access skill management and prompt description input fields.Affected if Non-admin or unauthenticated users have access to prompt description input functionality
You are affected if AstrBot version 4.23.6 is installed and the skill management interface with prompt description input is accessible to users who can supply unsanitized content.
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 robust input validation and sanitization in the _sanitize_prompt_description function, using allowlist validation and proper encoding to prevent injection attacks. Consider applying the principle of least privilege to the skill manager component.
- 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-10210 — 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-10210 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