# CVE-2026-41245: Junrar: Path Traversal (Zip-Slip) via Sibling Directory Name Prefix

> Attackers can write arbitrary files to sibling directories via crafted RAR archives, potentially leading to code execution or data modification.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Apr 2026
- **Updated:** 18 Aug 2026
- **Also known as:** ECHO-ec3d-99b8-6cf1, GHSA-hf5p-q87m-crj7, RHLW-2026-ed15c0b8d4d51966

## What is CVE-2026-41245?

CVE-2026-41245 is a medium-severity path traversal vulnerability in junrar, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 7.5.10 fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-41245?

2 open source packages ship an affected version, including com.github.junrar:junrar. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.junrar:junrar` | Maven | All versions | 7.5.10 |
| `com.github.junrar:junrar` | Maven | All versions | 7.5.10 |

Products: Junrar Project Junrar.

## How do I fix CVE-2026-41245?

Upgrade com.github.junrar:junrar to 7.5.10 or later.

## Is CVE-2026-41245 being exploited?

There is no known exploitation of CVE-2026-41245 in the wild and no public exploit code.

## Other vulnerabilities in junrar

- [CVE-2022-23596](https://insights.sbomify.com/CVE-2022-23596/): Infinite loop in junrar (high 7.5)
- [CVE-2026-28208](https://insights.sbomify.com/CVE-2026-28208/): Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix (medium 5.9)
- [CVE-2018-12418](https://insights.sbomify.com/CVE-2018-12418/): Junrar vulnerable to Infinite Loop (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41245 and fix it if it is affected.

What it is: CVE-2026-41245 is a medium-severity path traversal vulnerability in junrar, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41245 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.5.10
- com.github.junrar:junrar (Maven): affected all versions; fixed in 7.5.10

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41245/ (Markdown: https://insights.sbomify.com/CVE-2026-41245/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41245
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41245
- OSV: https://osv.dev/vulnerability/CVE-2026-41245

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41245/
Summaries are generated and may contain mistakes; the official description above is the record.