{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39246 exists.","fix":"No fix has been published for CVE-2026-39246 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39246 is a high-severity path traversal vulnerability in n/a, published on 9 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-39246 and fix it if it is affected.\n\nWhat it is: CVE-2026-39246 is a high-severity path traversal vulnerability in n/a, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39246 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-39246/ (Markdown: https://insights.sbomify.com/CVE-2026-39246/index.md)","id":"CVE-2026-39246","markdown":"https://insights.sbomify.com/CVE-2026-39246/index.md","name":"CVE-2026-39246","record":{"aliases":["GHSA-m5fg-qjq5-56fv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js decompression library","requires_auth":"none","summary":"Attackers can create arbitrary symlinks during archive extraction, leading to information disclosure of sensitive files outside the target directory.","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":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"decompress before 4.2.2 allows arbitrary symlink creation during archive extraction. When processing symlink entries (type === 'symlink'), the x.linkname field from the archive is passed directly to fs.symlink() without validation (index.js line 121). The preventWritingThroughSymlink check on line 98 only applies to file entries, not symlink creation. An attacker can craft an archive with symlink entries pointing to sensitive files outside the extraction directory (e.g., /etc/passwd), enabling information disclosure when the application reads the extracted contents.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Path traversal in n/a","id":"CVE-2026-39246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2026-39250"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2026-39245"},"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":6.2,"headline":"Path traversal in n/a","id":"CVE-2026-39245","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["n/a"]},"summary":"Attackers can create arbitrary symlinks during archive extraction, leading to information disclosure of sensitive files outside the target directory.","url":"https://insights.sbomify.com/CVE-2026-39246/"}