dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-15499

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
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 5 weeks old

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 security flaw has been discovered in AstrBotDevs AstrBot up to 4.25.2. Affected is the function FutureTaskTool.call of the file astrbot/core/tools/cron_tools.py of the component Scheduled Task Handler. Performing a manipulation of the argument payload["note"] results in improper authorization. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. 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

AstrBot up to 4.25.2 contains an improper authorization vulnerability in the Scheduled Task Handler (astrbot/core/tools/cron_tools.py). The FutureTaskTool.call function fails to properly validate the payload["note"] argument, allowing remote attackers to bypass authorization checks through manipulation of this parameter.

MitigationImplement proper authorization validation for the payload["note"] argument in the FutureTaskTool.call function. Until a vendor patch is available, restrict access to the scheduled task functionality to trusted users only and monitor for unauthorized task creation 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. Identify AstrBot installation and version
    Run 'pip show astrbot' or check your package manager to determine the installed version of AstrBot. Compare it to the affected range (up to 4.25.2).
    Affected if The installed version is 4.25.2 or lower.
  2. Locate the vulnerable cron_tools.py file
    Search for the file astrbot/core/tools/cron_tools.py in your AstrBot installation directory. This is the component containing the FutureTaskTool.call function.
    Affected if The file exists and the installed AstrBot version is within the affected range.
  3. Inspect the FutureTaskTool.call function
    Open cron_tools.py and locate the FutureTaskTool.call method. Examine whether it performs authorization validation on the payload['note'] parameter.
    Affected if The function lacks proper authorization validation for payload['note'].
  4. Determine if scheduled task functionality is exposed
    Check your AstrBot configuration and access controls to determine whether the scheduled task handler (FutureTaskTool) is accessible to untrusted users or remote attackers.
    Affected if Scheduled task functionality is accessible to untrusted or unauthenticated users.
  5. Review logs for unauthorized task creation attempts
    Search AstrBot logs for suspicious task creation events, particularly those where the 'note' parameter may have been manipulated to bypass authorization checks.
    Affected if Log entries show task creation attempts with manipulated 'note' parameters or unexpected task creation by untrusted users.

You are affected if AstrBot version 4.25.2 or lower is installed and the scheduled task handler is accessible to untrusted users without proper authorization validation on the payload['note'] parameter.

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 proper authorization validation for the payload["note"] argument in the FutureTaskTool.call function. Until a vendor patch is available, restrict access to the scheduled task functionality to trusted users only and monitor for unauthorized task creation 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-15499 — 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-15499 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