{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-14191 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-14191 is a high-severity memory corruption vulnerability in RARLAB RAR, published on 1 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-14191 and fix it if it is affected.\n\nWhat it is: CVE-2026-14191 is a high-severity memory corruption vulnerability in RARLAB RAR, published on 1 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-14191 in the wild and no public exploit code.\n\nAffected product: RARLAB RAR. 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-14191/ (Markdown: https://insights.sbomify.com/CVE-2026-14191/index.md)","id":"CVE-2026-14191","markdown":"https://insights.sbomify.com/CVE-2026-14191/index.md","name":"CVE-2026-14191","record":{"aliases":["BELL-CVE-2026-14191","DEBIAN-CVE-2026-14191","GHSA-5hjj-fvq6-8j36","UBUNTU-CVE-2026-14191"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WinRAR archive utility","requires_auth":"none","summary":"Attackers can achieve code execution by tricking users into repairing or testing a crafted RAR5 recovery volume set, corrupting heap memory.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"securin","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed in WinRAR / RAR 7.23.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-07T09:40:04Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-14191","stars":0,"title":"CVE-2026-14191 - Draft"}],"tier":"poc_unverified"},"has_fix":true,"headline":"WinRAR / UnRAR RAR5 recovery-volume (.rev) out-of-bounds heap write in RecVolumes5::ReadHeader","id":"CVE-2026-14191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Stored XSS in Bilin Software's HUMANIST Digital Human Resources","id":"CVE-2026-14192"},"packages":[],"prev":{"headline":"Sina Extension for Elementor \u003c 3.10.2 - Reflected XSS","id":"CVE-2026-14190"},"products":["RAR","UnRAR","UnRAR.dll","WinRAR"],"published":"2026-07-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["RARLAB"]},"summary":"Attackers can achieve code execution by tricking users into repairing or testing a crafted RAR5 recovery volume set, corrupting heap memory.","url":"https://insights.sbomify.com/CVE-2026-14191/"}