{"answers":{"affected":"4 open source packages ship an affected version, including compressing. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40931 exists.","fix":"Upgrade compressing to a fixed version for your release line: 1.10.5 or 2.1.1.","what":"CVE-2026-40931 is a high-severity path traversal vulnerability in node-modules compressing, published on 21 Apr 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-40931 and fix it if it is affected.\n\nWhat it is: CVE-2026-40931 is a high-severity path traversal vulnerability in node-modules compressing, published on 21 Apr 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-40931 exists.\n\nAffected packages and fixed versions:\n- compressing (npm): affected all versions; fixed in 1.10.5\n- compressing (npm): affected all versions; fixed in 1.10.5\n- compressing (npm): affected from 2.0.0; fixed in 2.1.1\n- compressing (npm): affected from 2.0.0; fixed in 2.1.1\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-40931/ (Markdown: https://insights.sbomify.com/CVE-2026-40931/index.md)","id":"CVE-2026-40931","markdown":"https://insights.sbomify.com/CVE-2026-40931/index.md","name":"CVE-2026-40931","record":{"aliases":["GHSA-4c3q-x735-j3r5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js compression library","requires_auth":"none","summary":"Attackers can bypass path validation in the compressing library using symlink poisoning to read or modify files outside the intended directory.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"compressing","vendor":"node-modules"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Compressing is a compressing and uncompressing lib for node. Prior to 2.1.1 and 1.10.5, the patch for CVE-2026-24884 relies on a purely logical string validation within the isPathWithinParent utility. This check verifies if a resolved path string starts with the destination directory string but fails to account for the actual filesystem state. By exploiting this \"Logical vs. Physical\" divergence, an attacker can bypass the security check using a Directory Poisoning technique (pre-existing symbolic links). This vulnerability is fixed in 2.1.1 and 1.10.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Complete Bypass of CVE-2026-24884 Patch via Git-Delivered Symlink Poisoning in compressing","id":"CVE-2026-40931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Flowise: Authenticated RCE Via MCP Adapters","id":"CVE-2026-40933"},"packages":[{"ecosystem":"npm","fixed":["1.10.5"],"introduced":["0"],"last_affected":[],"package":"compressing","purl":null,"source":"GHSA-4c3q-x735-j3r5"},{"ecosystem":"npm","fixed":["1.10.5"],"introduced":["0"],"last_affected":[],"package":"compressing","purl":"pkg:npm/compressing","source":"GHSA-4c3q-x735-j3r5"},{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["2.0.0"],"last_affected":[],"package":"compressing","purl":null,"source":"GHSA-4c3q-x735-j3r5"},{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["2.0.0"],"last_affected":[],"package":"compressing","purl":"pkg:npm/compressing","source":"GHSA-4c3q-x735-j3r5"}],"prev":{"headline":"LIBPNG: Chunk smuggling in push-mode APNG parser via unconsumed chunk body","id":"CVE-2026-40930"},"products":["compressing"],"published":"2026-04-21","related":[{"cvss_score":8.4,"headline":"Compressing Vulnerable to Arbitrary File Write via Symlink Extraction","id":"CVE-2026-24884","kev_date_added":null,"published":"2026-02-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"total"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["node-modules"]},"summary":"Attackers can bypass path validation in the compressing library using symlink poisoning to read or modify files outside the intended directory.","url":"https://insights.sbomify.com/CVE-2026-40931/"}