{"action":"Upgrade apache-iotdb to 2.0.8 or later.","affected":[{"fixed":"2.0.8","introduced":"1.3.3"}],"component":"apache-iotdb","cve_ids":["CVE-2026-24014"],"ecosystem":"PyPI","epss":0.0069,"exploited":false,"fixed_versions":["2.0.8"],"id":"tcs_01M5KGXC4EDYF9EW0X60CW7RZX","modified_at":"2026-07-08T11:30:04.762153892Z","published_at":"2026-07-06T09:16:35.270Z","references":["https://osv.dev/vulnerability/PYSEC-2026-2081","http://www.openwall.com/lists/oss-security/2026/07/06/12","https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m"],"severity":{"label":"critical","score":9.8},"sources":[{"source":"osv","source_id":"PYSEC-2026-2081","url":"https://osv.dev/vulnerability/PYSEC-2026-2081"}],"summary":"Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port i"}