NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕ Maven🐍 PyPI
Not in CISA KEV

Apache IoTDB Discloses Sensitive Information via Log FilesGHSA-5fc3-pqf2-57cx

Fix: apache/iotdb#14863

GHSA-5fc3-pqf2-57cx is a Information Exposure vulnerability in org.apache.iotdb:node-commons. A fix is available for org.apache.iotdb:node-commons — see the affected versions and patch details below.

Also known asCVE-2025-26864PYSEC-2025-60
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5fc3-pqf2-57cx.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.42%0.83%1.25%0.5%0.7%Jun 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected
☕org.apache.iotdb:node-commons☕org.apache.iotdb:node-commons🐍apache-iotdb🐍apache-iotdb

Real-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

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.iotdb:node-commons≥ 0.10.0&&< 1.3.41.3.4org.apache.iotdb:node-commons:1.3.4
☕Mavenorg.apache.iotdb:node-commons≥ 2.0.1-beta&&< 2.0.22.0.2org.apache.iotdb:node-commons:2.0.2
🐍PyPIapache-iotdb≥ 0.10.0&&< 1.3.41.3.4pip install --upgrade 'apache-iotdb==1.3.4'
🐍PyPIapache-iotdb≥ 2.0.1b0&&< 2.0.22.0.2pip install --upgrade 'apache-iotdb==2.0.2'

Affected Products

1 product · 2 configurations
Application
iotdbapache
≥ 0.10.0 && < 1.3.4
1 version
2.0.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.iotdb:node-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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 GHSA-5fc3-pqf2-57cx is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-5fc3-pqf2-57cx in your dependencies?

Find it across Maven, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache IoTDB Discloses Sensitive Information via Log Files