{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39245 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-39245 is a medium-severity path traversal vulnerability in n/a, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39245 and fix it if it is affected.\n\nWhat it is: CVE-2026-39245 is a medium-severity path traversal vulnerability in n/a, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39245 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-39245/ (Markdown: https://insights.sbomify.com/CVE-2026-39245/index.md)","id":"CVE-2026-39245","markdown":"https://insights.sbomify.com/CVE-2026-39245/index.md","name":"CVE-2026-39245","record":{"aliases":["GHSA-qcj4-cj8p-fhf4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js decompression library","requires_auth":"none","summary":"An attacker can exploit flawed path validation to write arbitrary files outside the intended directory, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"decompress","vendor":"decompress_project"}],"cvss":{"score":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"decompress before 4.2.2 contains an improper path containment check that enables directory traversal and arbitrary file write. The safeMakeDir function (index.js line 29) and the extraction path validation (index.js line 106) use String.indexOf() to verify the resolved path is within the output directory: realDestinationDir.indexOf(realOutputPath) !== 0. This check is flawed because it does not enforce a path separator boundary. For example, \"/tmp/app_config\".indexOf(\"/tmp/app\") returns 0, incorrectly passing the check even though /tmp/app_config is outside /tmp/app. Combined with the unvalidated symlink creation in the same package, an attacker can write arbitrary files to directories adjacent to the extraction target. This is a bypass of the fix for CVE-2020-12265. The correct check requires appending a path separator: realParentPath.indexOf(realOutputPath + path.sep) !== 0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Path traversal in n/a","id":"CVE-2026-39245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2026-39246"},"packages":[],"prev":{"headline":"adm-zip: Crafted ZIP file triggers 4GB memory allocation","id":"CVE-2026-39244"},"products":["n/a"],"published":"2026-07-09","related":[{"cvss_score":9.8,"headline":"Path Traversal in decompress","id":"CVE-2020-12265","kev_date_added":null,"published":"2020-04-26"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2026-39246","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":5.5,"headline":"decompress allows arbitrary hardlink creation during archive extraction","id":"CVE-2026-39243","kev_date_added":null,"published":"2026-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["n/a"]},"summary":"An attacker can exploit flawed path validation to write arbitrary files outside the intended directory, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-39245/"}