Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-41245 is a medium-severity Path Traversal (CWE-22) vulnerability in Junrar Project Junrar. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41245 is a path traversal vulnerability (CWE-22) in the Junrar open-source Java RAR archive library, affecting versions prior to 7.5.10. The flaw resides in the `LocalFolderExtractor` component, which mishandles crafted RAR archives during extraction, enabling attackers to write arbitrary files containing attacker-controlled content into sibling directories relative to the extraction target.
The vulnerability carries a CVSS v3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating a network-vector attack with high attack complexity but no privileges or user interaction required. Remote attackers can exploit it by tricking victims into extracting a malicious RAR archive processed by vulnerable Junrar instances, achieving arbitrary file writes outside the intended extraction directory and potentially leading to integrity compromises such as overwriting configuration files or injecting malicious scripts.
Mitigation is available via upgrade to Junrar version 7.5.10, which addresses the issue as detailed in the project's GitHub security advisory (GHSA-hf5p-q87m-crj7), release notes, and the fixing commit (d77e9a83eb721cd51f9c23d7869d0e6ad7f952d7). Security practitioners should audit applications using Junrar for unpatched versions and validate RAR inputs where possible.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23872
Vulnerability Data
Junrar is an open source java RAR archive library. Prior to version 7.5.10, a path traversal vulnerability in `LocalFolderExtractor` allows an attacker to write arbitrary files with attacker-controlled content into sibling directories when a crafted RAR archive is extracted. Version…
more
7.5.10 fixes the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Security testing in development catches path traversal via static/dynamic analysis.
Information access restriction limits which files an application may read or write.