# CVE-2025-26795: Apache IoTDB JDBC driver: Exposure of Sensitive Information in IoTDB JDBC driver > An attacker can access sensitive information exposed in log files by the Apache IoTDB JDBC driver, requiring an upgrade to secure the application. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 May 2025 - **Updated:** 19 May 2025 - **Also known as:** GHSA-gp98-hfvm-2r4x ## What is CVE-2025-26795? CVE-2025-26795 is a high-severity vulnerability in Apache IoTDB JDBC driver, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2025-26795? 4 open source packages ship an affected version, including org.apache.iotdb:iotdb-jdbc. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.iotdb:iotdb-jdbc` | Maven | From 0.10.0 | 1.3.4 | | `org.apache.iotdb:iotdb-jdbc` | Maven | From 0.10.0 | 1.3.4 | | `org.apache.iotdb:iotdb-jdbc` | Maven | From 2.0.1-beta | 2.0.2 | | `org.apache.iotdb:iotdb-jdbc` | Maven | From 2.0.1-beta | 2.0.2 | Products: Apache Iotdb. ## How do I fix CVE-2025-26795? Upgrade org.apache.iotdb:iotdb-jdbc to a fixed version for your release line: 1.3.4 or 2.0.2. ## Is CVE-2025-26795 being exploited? There is no known exploitation of CVE-2025-26795 in the wild and no public exploit code. ## Other vulnerabilities in Apache IoTDB JDBC driver - [CVE-2026-24014](https://insights.sbomify.com/CVE-2026-24014/): Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write (critical 9.8) - [CVE-2026-24015](https://insights.sbomify.com/CVE-2026-24015/): Apache IoTDB: Insecure Default Configuration Vulnerability (critical 9.8) - [CVE-2026-24713](https://insights.sbomify.com/CVE-2026-24713/): Apache IoTDB: JEXL Expression Injection Vulnerability (critical 9.8) - [CVE-2024-24780](https://insights.sbomify.com/CVE-2024-24780/): Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function (critical 9.8) - [CVE-2023-46226](https://insights.sbomify.com/CVE-2023-46226/): Apache IoTDB: Remote Code Execution (RCE) risk via the UDF (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-26795 and fix it if it is affected. What it is: CVE-2025-26795 is a high-severity vulnerability in Apache IoTDB JDBC driver, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-26795 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.iotdb:iotdb-jdbc (Maven): affected from 0.10.0; fixed in 1.3.4 - org.apache.iotdb:iotdb-jdbc (Maven): affected from 0.10.0; fixed in 1.3.4 - org.apache.iotdb:iotdb-jdbc (Maven): affected from 2.0.1-beta; fixed in 2.0.2 - org.apache.iotdb:iotdb-jdbc (Maven): affected from 2.0.1-beta; fixed in 2.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-26795/ (Markdown: https://insights.sbomify.com/CVE-2025-26795/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26795 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26795 - OSV: https://osv.dev/vulnerability/CVE-2025-26795 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-26795/ Summaries are generated and may contain mistakes; the official description above is the record.