CVE-2026-40009: Apache IoTDB privilege escalation via account renaming

CVE-2026-40009 · Severity: info · Published 2026-07-10

Apache IoTDB, a database designed for managing large amounts of time-series data, contains a security flaw that allows regular users to gain administrative control. By renaming their account to a specific internal system name, an authorized user can bypass security restrictions and access all data stored in the system. This could lead to unauthorized data modification or the exposure of sensitive industrial information.

Technologies: Apache Software Foundation IoTDB. Vendors: Apache Software Foundation.

Quick answers

Is CVE-2026-40009 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40009 being exploited in the wild.
How severe is CVE-2026-40009?
Informational severity, published 10 July 2026.
Which products and versions are affected?
Apache Software Foundation IoTDB 2.0.8 to 2.0.10.
Is there a fix for CVE-2026-40009?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-40009 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-40009?
Check whether you run Apache Software Foundation IoTDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A privilege escalation vulnerability exists in Apache IoTDB due to improper privilege management and access control (CWE-269, CWE-284). The flaw allows an authenticated user to escalate their privileges to full tree-path access by renaming their username to '__internal_auditor'. This suggests a logic error where the system grants elevated permissions based on a hardcoded or reserved string without verifying the actual identity or original authorization level of the user. The vulnerability affects versions 2.0.8 through 2.0.9 and is resolved in version 2.0.10.

Affected products

  • Apache IoTDB 2.0.8 to 2.0.10

Timeline

  • 2026-07-10: advisory: Initial disclosure by Apache Software Foundation
  • 2026-07-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.