Apache IoTDB JDBC driver: Insertion of Sensitive Information into Log File
CVE-2025-26795 is a high-severity insertion of sensitive information into log file vulnerability in Apache IoTDB JDBC driver from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.0.2 as the first without the flaw, so updating Apache IoTDB JDBC driver to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.76% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache IoTDB JDBC driver to 2.0.2 or a later version.
- Update Iotdb to 1.3.4 or 2.0.2, whichever matches your release line, or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache IoTDB JDBC driver | 0.10.0 through 1.3.3; 2.0.1-beta up to, but not including, 2.0.2 | 2.0.2 |
| Apache | Iotdb | 0.10.0 up to, but not including, 1.3.4; 2.0.1 up to, but not including, 2.0.2 | 1.3.4, 2.0.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).
Official description
Exposure of Sensitive Information to an Unauthorized Actor, Insertion of Sensitive Information into Log File vulnerability in Apache IoTDB JDBC driver. This issue affects iotdb-jdbc: from 0.10.0 through 1.3.3, from 2.0.1-beta before 2.0.2. Users are recommended to upgrade to version 2.0.2 and 1.3.4, which fix the issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- openwall.com/lists/oss-security/2025/05/14/3Mailing List, Third Party Advisory
Other vulnerabilities in Apache IoTDB JDBC driver
- 7.5 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.6 High severity
- 7.5 High severity
- 8.2 High severity
- 7.6 High severity
- 4.6 Medium severity
- 7.5 High severity
Spotted an error? Tell us.