CVE-2026-24013
Auth bypass via forged sessionId in Apache IoTDB Thrift RPC.
Is CVE-2026-24013 being exploited?
Not confirmed. CVE-2026-24013 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-24013?
CVE-2026-24013 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24013?
Yes. A fix has been recorded for CVE-2026-24013. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24013 affect?
CVE-2026-24013 affects Apache IoTDB 1.3.3–2.0.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24013?
Upgrade to IoTDB 2.0.8+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authentication bypass lets attacker read time-series data without openSession auth via forged sessionId.
Immediate action required
- affected>= 1.3.3 and < 2.0.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.