# CVE-2026-28208: Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix

> Attackers can write arbitrary files via crafted RAR archives in Junrar, potentially leading to remote code execution on Linux/Unix systems.

- **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:** 26 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** ECHO-40b2-f523-98e1, GHSA-j273-m5qq-6825

## What is CVE-2026-28208?

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.

### Official 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.

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

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

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.8 |
| `com.github.junrar:junrar` | Maven | All versions | 7.5.8 |

Products: Junrar Project Junrar.

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

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

## Is CVE-2026-28208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28208 exists.

## Other vulnerabilities in junrar

- [CVE-2022-23596](https://insights.sbomify.com/CVE-2022-23596/): Infinite loop in junrar (high 7.5)
- [CVE-2026-41245](https://insights.sbomify.com/CVE-2026-41245/): Junrar: Path Traversal (Zip-Slip) via Sibling Directory Name Prefix (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-28208 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28208 exists.

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

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-28208/ (Markdown: https://insights.sbomify.com/CVE-2026-28208/index.md)
```

## Sources

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

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