CVE-2025-26864
HIGHCVE-2025-26864 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.iotdb:node-commons. O3 Security confirms whether CVE-2025-26864 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache IoTDB: Exposure of Sensitive Information in IoTDB OpenID Authentication
Real-World Exposure
org.apache.iotdb:node-commons☕org.apache.iotdb:node-commons🐍apache-iotdb🐍apache-iotdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.iotdb:node-commons | ≥ 0.10.0&&< 1.3.4 | 1.3.4 |
| ☕Maven | org.apache.iotdb:node-commons | ≥ 2.0.1-beta&&< 2.0.2 | 2.0.2 |
| 🐍PyPI | apache-iotdb | ≥ 0.10.0&&< 1.3.4 | 1.3.4 |
| 🐍PyPI | apache-iotdb | ≥ 2.0.1b0&&< 2.0.2 | 2.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.iotdb:node-commons. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.iotdb:node-commons to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-26864 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-26864 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-26864. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-26864 in your dependencies?
O3 detects CVE-2025-26864 across Maven, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.