CVE-2025-48459

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.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2025-48459 has a CVSS score of 5.3 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.5); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2025-48459? CVE-2025-48459 is a critical-severity insecure deserialization vulnerability in org.apache.iotdb:iotdb-confignode (maven), affecting versions >= 1.0.0, < 2.0.5. It is fixed in 2.0.5. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2025-48459? CVE-2025-48459 has a CVSS score of 5.3 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-48459?
   • org.apache.iotdb:iotdb-confignode (maven) (versions >= 1.0.0, < 2.0.5)
   • apache-iotdb (pip) (versions >= 1.0.0, < 2.0.5)
4. Is there a fix for CVE-2025-48459? Yes. CVE-2025-48459 is fixed in 2.0.5. Upgrade to this version or later.
5. Is CVE-2025-48459 exploitable, and should I be worried? Whether CVE-2025-48459 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-48459 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-48459?
   • Upgrade org.apache.iotdb:iotdb-confignode to 2.0.5 or later
   • Upgrade apache-iotdb to 2.0.5 or later