{"answers":{"affected":"2 open source packages ship an affected version, including com.github.junrar:junrar.","exploited":"There is no known exploitation of CVE-2026-86071 in the wild and no public exploit code.","fix":"Upgrade com.github.junrar:junrar to 7.6.1 or later.","what":"CVE-2026-86071 is a low-severity path traversal vulnerability in junrar, published on 16 Sep 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-86071 and fix it if it is affected.\n\nWhat it is: CVE-2026-86071 is a low-severity path traversal vulnerability in junrar, published on 16 Sep 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-86071 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.6.1\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.6.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-86071/ (Markdown: https://insights.sbomify.com/CVE-2026-86071/index.md)","id":"CVE-2026-86071","markdown":"https://insights.sbomify.com/CVE-2026-86071/index.md","name":"CVE-2026-86071","record":{"aliases":["ECHO-3dd8-1d6e-83c7","GHSA-89m4-43j5-vhhx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java RAR archive library","requires_auth":"none","summary":"Attackers can create directories outside the extraction root via crafted RAR archives, potentially causing filesystem pollution or denial of service.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Junrar is an open source Java RAR archive library. Prior to version 7.6.1, LocalFolderExtractor in src/main/java/com/github/junrar/LocalFolderExtractor.java can create directories outside the intended extraction root when processing a crafted archive entry. LocalFolderExtractor.createFile() validates only the final canonical file path, while LocalFolderExtractor.makeFile() creates intermediate path segments with unchecked mkdir() calls. An entry can therefore make the final path resolve inside the destination while causing intermediate directory creation outside it, enabling filesystem pollution or file-versus-directory squatting that can make later security-sensitive writes fail. The demonstrated impact is directory creation, not unconditional arbitrary file-content write. This issue is fixed in version 7.6.1.","ecosystems":["Maven"],"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":"Junrar: LocalFolderExtractor mkdir escape allows directory creation outside extraction root","id":"CVE-2026-86071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution","id":"CVE-2026-86073"},"packages":[{"ecosystem":"Maven","fixed":["7.6.1"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":null,"source":"GHSA-89m4-43j5-vhhx"},{"ecosystem":"Maven","fixed":["7.6.1"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":"pkg:maven/com.github.junrar/junrar","source":"GHSA-89m4-43j5-vhhx"}],"prev":{"headline":"Horilla attendance approval endpoint is vulnerable to cross-site request forgery","id":"CVE-2026-86066"},"products":["junrar"],"published":"2026-09-16","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["junrar"]},"summary":"Attackers can create directories outside the extraction root via crafted RAR archives, potentially causing filesystem pollution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-86071/"}