dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-10212

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was identified in AstrBotDevs AstrBot 4.24.2. This affects the function astr_main_agent of the file astrbot/core/astr_main_agent.py. Such manipulation of the argument session_id leads to authorization bypass. It is possible to launch the attack remotely. The exploit is publicly available and might 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 confidence

An authorization bypass vulnerability exists in AstrBot 4.24.2 where manipulation of the session_id argument in the astr_main_agent function allows attackers to bypass authentication controls. The flaw enables remote attackers to access protected functionality without proper authorization. The exploit is publicly available, increasing exploitation risk.

MitigationImplement strict session_id validation and authorization checks in the astr_main_agent function. Since the vendor has not responded to disclosure, organizations should network-segment the service, implement additional authentication layers, and monitor for exploitation attempts.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate AstrBot installation
    Search for the astrbot directory or check common installation paths such as /opt/astrbot, /usr/local/astrbot, or the current working directory where AstrBot may have been installed.
    Affected if The astrbot directory with core/astr_main_agent.py does not exist - the product is not installed.
  2. Identify installed AstrBot version
    Check for a version file, package.json, setup.py, or git tags in the AstrBot installation directory. Run 'git describe --tags' if it's a git repository, or inspect version information in any version metadata files.
    Affected if The installed version is 4.24.2 exactly, or if version cannot be determined but the vulnerable file exists.
  3. Verify vulnerable file exists
    Confirm the presence of astrbot/core/astr_main_agent.py in the installation directory.
    Affected if The file astrbot/core/astr_main_agent.py exists - this indicates the potentially vulnerable component is present.
  4. Inspect astr_main_agent function
    Open astrbot/core/astr_main_agent.py and locate the astr_main_agent function definition. Check if it accepts a session_id parameter and examine how session_id is processed.
    Affected if The function accepts session_id as a parameter without proper validation that the session belongs to the authenticated user.
  5. Check API or service exposure
    Determine if the astr_main_agent function or its containing module is exposed via an API endpoint, web service, or any network-accessible interface. Review routing configurations or entry points that invoke this function.
    Affected if The function is exposed via an API or web endpoint that accepts user-controlled session_id input.

A user is affected if AstrBot version 4.24.2 is installed, the astr_main_agent function accepts session_id without validating ownership, and this function is exposed through an accessible interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict session_id validation and authorization checks in the astr_main_agent function. Since the vendor has not responded to disclosure, organizations should network-segment the service, implement additional authentication layers, and monitor for exploitation attempts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10212 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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