https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:40:44 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-259968 EUVD-2026-259968 https://cve.radiocsirt.org/vuln/euvd-2026-259968 https://cve.radiocsirt.org/vuln/fkie_cve-2025-48459 <p>Deserialization of Untrusted Data vulnerability in Apache IoTDB.</p> <p>This issue affects Apache IoTDB: from 1.0.0 before 2.0.5.</p> <p>Users are recommended to upgrade to version 2.0.5, which fixes the issue.</p> <p>Deserialization of Untrusted Data vulnerability in Apache IoTDB.</p> <p>This issue affects Apache IoTDB: from 1.0.0 before 2.0.5.</p> <p>Users are recommended to upgrade to version 2.0.5, which fixes the issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-48459 https://cve.radiocsirt.org/vuln/ghsa-776q-jw43-fhjx <p><strong>Affected:</strong> Maven: org.apache.iotdb:iotdb-confignode, PyPI: apache-iotdb</p> <p>### Summary</p> <p>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.</p> <p>### Affected</p> <p>Apache IoTDB **from 1.0.0 before 2.0.5**.</p> <p>### Remediation</p> <p>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.</p> <p><strong>Affected:</strong> Maven: org.apache.iotdb:iotdb-confignode, PyPI: apache-iotdb</p> <p>### Summary</p> <p>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.</p> <p>### Affected</p> <p>Apache IoTDB **from 1.0.0 before 2.0.5**.</p> <p>### Remediation</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-776q-jw43-fhjx https://cve.radiocsirt.org/vuln/pysec-2025-88 <p><strong>Affected:</strong> PyPI: apache-iotdb</p> <p>Deserialization of Untrusted Data vulnerability in Apache IoTDB.</p> <p>This issue affects Apache IoTDB: from 1.0.0 before 2.0.5.</p> <p>Users are recommended to upgrade to version 2.0.5, which fixes the issue.</p> <p><strong>Affected:</strong> PyPI: apache-iotdb</p> <p>Deserialization of Untrusted Data vulnerability in Apache IoTDB.</p> <p>This issue affects Apache IoTDB: from 1.0.0 before 2.0.5.</p> <p>Users are recommended to upgrade to version 2.0.5, which fixes the issue.</p> https://cve.radiocsirt.org/vuln/pysec-2025-88