● Medium · CVSS 5.9

How to Fix CVE-2026-28208: Path traversal in junrar

Q: What is the CVSS score for CVE-2026-28208?

5.9 (Medium). Vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`.

Q: Where is the official advisory for CVE-2026-28208?

The vendor advisory is at [https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825](https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28208.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-28208 is a path traversal in junrar junrar. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	5.9 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	junrar < 7.5.8
Fixed in	See vendor advisory
Type (CWE)	CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-28208?

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. The CVSS base score is 5.9 (Medium). The official advisory is at https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825.

Am I affected?

Check the version of junrar you are running and compare it against the Affected row above (junrar < 7.5.8). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s junrar 2>/dev/null | grep -i ^Version
rpm -q junrar 2>/dev/null
command -v junrar >/dev/null && junrar --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*junrar*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "junrar" 2>$null

How to fix CVE-2026-28208

Upgrade junrar to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade junrar
dpkg -s junrar | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh junrar -y
# or for older releases:
sudo yum update junrar -y
rpm -q junrar

SUSE / openSUSE


sudo zypper refresh
sudo zypper update junrar
rpm -q junrar

Node.js / npm


# Update the affected package in your project
npm install junrar@latest
npm ls junrar
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-28208 affecting junrar
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-28208-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*junrar*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\junrar-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\junrar" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "junrar" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "junrar"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-28208 affecting junrar
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-28208-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s junrar 2>/dev/null | grep -i ^Version || echo "junrar not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q junrar || echo "junrar not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-28208-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/junrar /etc/junrar.d /etc/junrar.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y junrar
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y junrar
elif command -v yum >/dev/null; then
    yum update -y junrar
elif command -v zypper >/dev/null; then
    zypper --non-interactive update junrar
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s junrar 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q junrar
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-28208" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-28208"

Disable the affected service (Linux)


sudo systemctl stop junrar 2>/dev/null || true
sudo systemctl disable junrar 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s junrar 2>/dev/null | grep -i ^Version
rpm -q junrar 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*junrar*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-8751: Deserialization RCE in h2o-3 — Deserialization RCE in h2o-3
How to Fix CVE-2026-27994: Improper control of filename for include/require statement in php program ('php. — Improper control of filename for include/require statement in php program ('php.
How to Fix CVE-2026-25357: Authentication Bypass in Ultimate Membership Pro , Authentication Bypass in Ultimate Membership Pro
How to Fix CVE-2026-4214: D-Link DNS-1550-04 app_mgr.cgi UPnP_AV_Server_Path_Setting stack-based overflow , D-Link DNS-1550-04 app_mgr.cgi UPnP_AV_Server_Path_Setting stack-based overflow
How to Fix CVE-2026-43532: Incomplete List of Disallowed Inputs in OpenClaw , Incomplete List of Disallowed Inputs in OpenClaw

Is CVE-2026-28208 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-28208?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-28208?

5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.

Where is the official advisory for CVE-2026-28208?

The vendor advisory is at https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28208.

References

Official vendor advisory: https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28208
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/junrar/junrar/commit/947ff1d33f00f940aa68ae2593500291d799d954
Additional reference: https://github.com/junrar/junrar/releases/tag/v7.5.8

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*