CVE-2026-15499

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-12. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
10.2%
KEV
Not listed

Published

July 12, 2026

Last Modified

July 13, 2026

Advisory Details (1)

Auto-updated Jul 12, 2026
No patch confirmed yet.
generic

AstrBot: Improper ownership checks in `future_task` allow same-session users to modify other users’ scheduled tasks and retain victim-derived cron privileges · GitHub

https://gist.github.com/YLChen-007/2bab96d5bedef784f90c97009fff8a19

Vendor Advisories for CVE-2026-15499(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-16 14:55 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 14:08 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 13:23 UTCGHSA enrichment
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 16:24 UTCNVD updateCVSS v4 → 2.1
  17. 2026-07-13 15:32 UTCMITRE cvelistV5CVSS v4 → 5.3
  18. 2026-07-13 12:38 UTCGHSA enrichment
  19. 2026-07-12 14:07 UTCNVD updateCVSS v4 → 2.1
  20. 2026-07-12 11:52 UTCEG score recompute
  21. 2026-07-12 11:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15499?
CVE-2026-15499 is a medium vulnerability published on July 12, 2026. 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.…
When was CVE-2026-15499 disclosed?
CVE-2026-15499 was first published in the National Vulnerability Database on July 12, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15499 actively exploited?
CVE-2026-15499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15499?
CVE-2026-15499 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-15499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15499, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15499

Explore →

Is Your Infrastructure Affected by CVE-2026-15499?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.