CVE-2025-26864GHSA-5FC3-PQF2-57CXPYSEC-2025-60
Apache IoTDB: Exposure of Sensitive Information in IoTDB OpenID Authentication
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Fix
- Fixed in 2.0.2, 1.3.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Exposure of Sensitive Information to an Unauthorized Actor, Insertion of Sensitive Information into Log File vulnerability in the OpenIdAuthorizer of Apache IoTDB. This issue affects Apache IoTDB: from 0.10.0 through 1.3.3, from 2.0.1-beta before 2.0.2. Users are recommended to upgrade to version 1.3.4 and 2.0.2, which fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache IoTDB
From 0.10.0 · through 1.3.3; From 2.0.1-beta · fixed in 2.0.2
- org.apache.iotdb:node-commonsMaven
From 0.10.0 · fixed in 1.3.4
- org.apache.iotdb:node-commonsMaven
From 2.0.1-beta · fixed in 2.0.2
- apache-iotdbPyPI
From 0.10.0 · fixed in 1.3.4
- apache-iotdbPyPI
From 2.0.1b0 · fixed in 2.0.2