CVE-2026-24015: Apache IoTDB: Insecure Default Configuration Vulnerability
Published Mar 9, 2026
·Updated
A vulnerability in Apache IoTDB.
This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before 2.0.7.
Users are recommended to upgrade to version 1.3.7 or 2.0.7, which fixes the issue.
Affected Software
5 affected componentsFixes available
Apache IoTDB>=1.0.0<1.3.7, >=2.0.0<2.0.7
Apache IoTDB>=1.0.0<1.3.7
Apache IoTDB>=2.0.0<2.0.7
maven/org.apache.iotdb:iotdb-core>=2.0.0<2.0.7
2.0.7
maven/org.apache.iotdb:iotdb-core>=1.0.0<1.3.7
1.3.7
Event History
Mar 9, 2026
CVE Published
via MITRE·08:57 AM
Data Sourced
via MITRE·08:57 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:30 AM
Data Sourced
via GitHub·09:30 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-24015?
CVE-2026-24015 is classified as a medium severity vulnerability due to insecure default configurations in Apache IoTDB.
2
How do I fix CVE-2026-24015?
To fix CVE-2026-24015, upgrade to Apache IoTDB version 1.3.7 or 2.0.7.
3
Which versions of Apache IoTDB are affected by CVE-2026-24015?
CVE-2026-24015 affects Apache IoTDB versions prior to 1.3.7 and 2.0.7.
4
What impact does CVE-2026-24015 have on users?
CVE-2026-24015 can potentially expose users to unauthorized access and configuration issues due to insecure defaults.
5
Is there any workaround for CVE-2026-24015?
There are no known workarounds; the recommended action is to upgrade to the fixed versions.