{"answers":{"affected":"2 open source packages ship an affected version, including com.github.junrar:junrar. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28208 exists.","fix":"Upgrade com.github.junrar:junrar to 7.5.8 or later.","what":"CVE-2026-28208 is a medium-severity path traversal vulnerability in junrar, published on 26 Feb 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-28208 and fix it if it is affected.\n\nWhat it is: CVE-2026-28208 is a medium-severity path traversal vulnerability in junrar, published on 26 Feb 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-28208 exists.\n\nAffected packages and fixed versions:\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.5.8\n- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.5.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-28208/ (Markdown: https://insights.sbomify.com/CVE-2026-28208/index.md)","id":"CVE-2026-28208","markdown":"https://insights.sbomify.com/CVE-2026-28208/index.md","name":"CVE-2026-28208","record":{"aliases":["ECHO-40b2-f523-98e1","GHSA-j273-m5qq-6825"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java RAR library","requires_auth":"none","summary":"Attackers can write arbitrary files via crafted RAR archives in Junrar, potentially leading to remote code execution on Linux/Unix systems.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"junrar","vendor":"junrar_project"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/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":"Junrar is an open source java RAR archive library. Prior to version 7.5.8, a backslash path traversal vulnerability in `LocalFolderExtractor` allows an attacker to write arbitrary files with attacker-controlled content anywhere on the filesystem when a crafted RAR archive is extracted on Linux/Unix. This can often lead to remote code execution (e.g., overwriting shell profiles, source code, cron jobs, etc). Version 7.5.8 has a fix for the issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix","id":"CVE-2026-28208","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":"FreePBX: Command Injection leading to Remote Code Execution in FreePBX ElevenLabs Text-to-Speech integration","id":"CVE-2026-28209"},"packages":[{"ecosystem":"Maven","fixed":["7.5.8"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":null,"source":"GHSA-j273-m5qq-6825"},{"ecosystem":"Maven","fixed":["7.5.8"],"introduced":["0"],"last_affected":[],"package":"com.github.junrar:junrar","purl":"pkg:maven/com.github.junrar/junrar","source":"GHSA-j273-m5qq-6825"}],"prev":{"headline":"Zen-C Vulnerable to Command Injection via Malicious Output Filename","id":"CVE-2026-28207"},"products":["junrar"],"published":"2026-02-26","related":[{"cvss_score":7.5,"headline":"Infinite loop in junrar","id":"CVE-2022-23596","kev_date_added":null,"published":"2022-02-01"},{"cvss_score":5.9,"headline":"Junrar: Path Traversal (Zip-Slip) via Sibling Directory Name Prefix","id":"CVE-2026-41245","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":5.5,"headline":"Junrar vulnerable to Infinite Loop","id":"CVE-2018-12418","kev_date_added":null,"published":"2018-06-14"}],"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-03-02","vendors":["junrar"]},"summary":"Attackers can write arbitrary files via crafted RAR archives in Junrar, potentially leading to remote code execution on Linux/Unix systems.","url":"https://insights.sbomify.com/CVE-2026-28208/"}