IotdbApplication · Apache
CVE-2025-26795
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Apache IoTDB JDBC driver (versions 0.10.0 through 1.3.3 and 2.0.1-beta before 2.0.2) contains a vulnerability where sensitive information is either exposed to unauthorized actors or inadvertently written to log files, allowing potential attackers to obtain credentials or other sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
IotdbApplication
>= 0.10.0, < 1.3.4>= 2.0.1, < 2.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the iotdb-jdbc library versionInspect your project's dependency manifest: check pom.xml for <artifactId>iotdb-jdbc</artifactId> or build.gradle for 'iotdb-jdbc' dependency. If using compiled JARs, check the filename or run 'jar -xvf iotdb-jdbc-*.jar' and inspect the manifest file.Affected if The reported version falls within 0.10.0 through 1.3.3, or 2.0.1-beta through 2.0.1 (anything less than 1.3.4 or 2.0.2).
-
Confirm JDBC driver is in useSearch your codebase for imports of org.apache.iotdb.jdbc.* or references to IoTDBConnection, or check if the application explicitly loads the IoTDB JDBC driver class.Affected if The application imports or uses any IoTDB JDBC driver classes.
-
Review logging configurationExamine your logging configuration files (log4j.xml, logback.xml, log4j2.xml) for any logger rules targeting org.apache.iotdb or the JDBC driver package, particularly DEBUG or TRACE level settings.Affected if DEBUG or TRACE logging is enabled for the IoTDB JDBC driver package, which could cause credential exposure to logs.
-
Scan application logs for credential leakageSearch your log directories for patterns matching JDBC connection parameters: look for strings containing 'user=', 'password=', 'token=', 'iotdb', or JDBC connection URLs that may contain embedded credentials.Affected if Log files contain any JDBC connection strings, user credentials, tokens, or session tokens that originated from the IoTDB driver.
You are affected if your iotdb-jdbc version is 0.10.0 to 1.3.3 or 2.0.1-beta to 2.0.1, AND your application logs DEBUG/TRACE output from the JDBC driver or has logged connection strings containing credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.42.0.2
Upgrade the iotdb-jdbc library to version 1.3.4 or 2.0.2 or later to resolve the sensitive information exposure vulnerability.
1.3.4 (for 0.10.0-1.3.x) or 2.0.2 (for 2.0.1-2.0.1-beta)
- 1. Identify the current version of iotdb-jdbc in use by checking project dependencies (e.g., pom.xml, build.gradle, or Maven/Gradle dependencies)
- 2. For versions 0.10.0 through 1.3.3: upgrade iotdb-jdbc dependency to version 1.3.4
- 3. For versions 2.0.1 through 2.0.1-beta: upgrade iotdb-jdbc dependency to version 2.0.2
- 4. Rebuild and redeploy the application with the new dependency version
- 5. Verify that the application functions correctly with the new JDBC driver version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Iotdb
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data