{"answers":{"affected":"1 open source package ship an affected version, including apache-iotdb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24014 in the wild and no public exploit code.","fix":"Upgrade apache-iotdb to 2.0.8 or later.","what":"CVE-2026-24014 is a critical path traversal vulnerability in Apache IoTDB, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24014 and fix it if it is affected.\n\nWhat it is: CVE-2026-24014 is a critical path traversal vulnerability in Apache IoTDB, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24014 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- apache-iotdb (PyPI): affected from 1.3.3; fixed in 2.0.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24014/ (Markdown: https://insights.sbomify.com/CVE-2026-24014/index.md)","id":"CVE-2026-24014","markdown":"https://insights.sbomify.com/CVE-2026-24014/index.md","name":"CVE-2026-24014","record":{"aliases":["GHSA-rpg4-r93p-w6gg","PYSEC-2026-2081"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache IoTDB","requires_auth":"none","summary":"An attacker with network access to the internal RPC port can write arbitrary files via path traversal in the Trigger JAR name, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"iotdb","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"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 is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process.\n\nThis issue affects Apache IoTDB: from 1.3.3 before 2.0.8.\n\nUsers are recommended to upgrade to version 2.0.8, which fixes the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write","id":"CVE-2026-24014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Apache IoTDB: Insecure Default Configuration Vulnerability","id":"CVE-2026-24015"},"packages":[{"ecosystem":"PyPI","fixed":["2.0.8"],"introduced":["1.3.3"],"last_affected":[],"package":"apache-iotdb","purl":"pkg:pypi/apache-iotdb","source":"PYSEC-2026-2081"}],"prev":{"headline":"Apache IoTDB: Authentication Bypass via Forged SessionID in Thrift RPC","id":"CVE-2026-24013"},"products":["Apache IoTDB"],"published":"2026-07-06","related":[{"cvss_score":9.8,"headline":"Apache IoTDB: Insecure Default Configuration Vulnerability","id":"CVE-2026-24015","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.8,"headline":"Apache IoTDB: JEXL Expression Injection Vulnerability","id":"CVE-2026-24713","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.8,"headline":"Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function","id":"CVE-2024-24780","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":9.8,"headline":"Apache IoTDB: Remote Code Execution (RCE) risk via the UDF","id":"CVE-2023-46226","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":9.8,"headline":"Apache IoTDB: Unsafe deserialize map in Sync Tool","id":"CVE-2023-51656","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"Apache IoTDB grafana-connector Login Bypass Vulnerability","id":"CVE-2023-24831","kev_date_added":null,"published":"2023-04-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["Apache Software Foundation"]},"summary":"An attacker with network access to the internal RPC port can write arbitrary files via path traversal in the Trigger JAR name, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-24014/"}