Security readout for executives and security teams
Plain-English summary
CVE-2026-28208 affects Junrar, a Java library for extracting RAR archives. Before version 7.5.8, crafted archive paths can bypass Linux/Unix path checks and write files outside the intended extraction folder. Business risk is highest where applications automatically extract untrusted RAR files, because file overwrite can enable serious follow-on impact.
Executive priority
Prioritize remediation for internet-facing or automated archive-processing systems. Treat as high urgency where untrusted RAR files are extracted, because arbitrary file write can become code execution depending on runtime permissions and file locations.
Technical view
Junrar LocalFolderExtractor before 7.5.8 has a CWE-22 path traversal issue involving backslash handling on Linux/Unix. A crafted RAR archive can cause attacker-controlled file writes to arbitrary filesystem locations during extraction. The advisory notes this can often lead to remote code execution through overwritten profiles, source code, cron jobs, or similar files.
Likely exposure
Exposure is likely in Java applications or services using junrar below 7.5.8 to extract RAR archives on Linux/Unix, especially when archives come from users, partners, email, uploads, or automated processing pipelines.
Exploitation context
The CVSS score is 5.9 with high attack complexity, but integrity impact is high. The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires a vulnerable extraction workflow and a crafted RAR reaching it.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, fix commit, and 7.5.8 release. Do not assume Windows impact from the provided description; the issue is specifically described for Linux/Unix extraction behavior.
Mitigation direction
- Upgrade junrar to version 7.5.8 or later.
- Identify applications that extract RAR files using junrar.
- Restrict or disable extraction of untrusted RAR archives until upgraded.
- Run extraction with least-privilege filesystem permissions.
- Review vendor advisory and release notes for implementation guidance.
Validation and detection
- Inventory Java dependencies for junrar versions below 7.5.8.
- Confirm affected systems run extraction on Linux or Unix.
- Trace archive ingestion paths accepting user-controlled RAR files.
- Verify deployed builds include junrar 7.5.8 or later.
- Review extraction service permissions and writable filesystem locations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28208 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/junrar/junrar/security/advisories/GHSA-j273-m5qq-6825CVE reference · x_refsource_CONFIRM
- https://github.com/junrar/junrar/commit/947ff1d33f00f940aa68ae2593500291d799d954CVE reference · x_refsource_MISC
- https://github.com/junrar/junrar/releases/tag/v7.5.8CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.