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

CVE-2025-48459 — iotdb-confignode

MEDIUMFix: apache/iotdb@5ad4a94

CVE-2025-48459 is a medium-severity (CVSS 5.3) Deserialization of Untrusted Data vulnerability in org.apache.iotdb:iotdb-confignode. A fix is available for org.apache.iotdb:iotdb-confignode — see the affected versions and patch details below.

Apache IoTDB: Deserialization of untrusted Data

Also known asGHSA-776q-jw43-fhjxPYSEC-2025-88
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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 CVE-2025-48459.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk+0.02%
Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk
0.00%0.36%0.72%1.07%0.6%0.5%May 26Oct 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.apache.iotdb:iotdb-confignode🐍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

Summary

Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process.

Affected

Apache IoTDB from 1.0.0 before 2.0.5.

Remediation

Upgrade to 2.0.5, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted networks and disable or sanitize any feature paths that accept serialized payloads. These mitigations are defense-in-depth only; upgrading to 2.0.5 is the definitive fix.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.iotdb:iotdb-confignode≥ 1.0.0&&< 2.0.52.0.5org.apache.iotdb:iotdb-confignode:2.0.5
🐍PyPIapache-iotdb≥ 1.0.0&&< 2.0.52.0.5pip install --upgrade 'apache-iotdb==2.0.5'

Affected Products

1 product · 1 configurations
Application
iotdbapache
≥ 1.0.0 && < 2.0.5
range

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:iotdb-confignode, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.iotdb:iotdb-confignode to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48459 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

### Summary Apache IoTDB deserializes data from external inputs without sufficient validation, allowing attacker-controlled serialized objects to be processed. In environments where a compatible gadget chain is reachable, this can be abused to execute arbitrary code or alter server state; at minimum it enables high-impact integrity and confidentiality compromise on the IoTDB process. ### Affected Apache IoTDB **from 1.0.0 before 2.0.5**. ### Remediation Upgrade to **2.0.5**, which addresses the flaw. If immediate upgrade is not possible, restrict exposure of IoTDB endpoints to trusted net
O3 Security · Impact-Aware SCA

Is CVE-2025-48459 in your dependencies?

Find it across Maven, PyPI, including transitive dependencies.

CVE-2025-48459: iotdb-confignode RCE — Fixed in 2.0.5