GHSA-89M4-43J5-VHHX
Vulnerability from github – Published: 2026-09-17 16:30 – Updated: 2026-09-17 16:30Summary
LocalFolderExtractor validates only the final canonical file path before extraction. However, makeFile() creates intermediate directories one path segment at a time without checking whether each created directory remains inside the destination folder.
A malicious RAR entry can make the final file path resolve inside the extraction destination, while causing intermediate mkdir() calls to create attacker-chosen directories outside the extraction root.
This is an extraction root escape via unchecked intermediate directory creation. The default impact is directory creation outside the intended destination, not unconditional arbitrary file content write.
Affected Code
src/main/java/com/github/junrar/LocalFolderExtractor.javacreateFile()checks only the final canonical path.makeFile()callsdir.mkdir()for each intermediate segment without containment checks.
Relevant code flow:
private File createFile(final FileHeader fh, final File destination) throws IOException {
String name = invariantSeparatorsPathString(fh.getFileName());
File f = new File(destination, name);
String dirCanonPath = f.getCanonicalPath();
if (!dirCanonPath.startsWith(destination.getCanonicalPath() + File.separator)) {
throw new IllegalStateException(...);
}
if (!f.exists()) {
f = makeFile(destination, name);
}
return f;
}
private File makeFile(final File destination, final String name) throws IOException {
final String[] dirs = name.split("/");
String path = "";
for (int i = 0; i < dirs.length - 1; i++) {
path = path + File.separator + dirs[i];
File dir = new File(destination, path);
dir.mkdir();
}
path = path + File.separator + dirs[dirs.length - 1];
final File f = new File(destination, path);
f.createNewFile();
return f;
}
Impact
An attacker who can supply a malicious RAR archive can create directories outside the intended extraction directory.
This violates the expected extraction boundary and can be used for filesystem pollution or file-vs-directory squatting. For example, an attacker can create a directory at a path where a later security-sensitive file is expected, causing future writes to that path to fail.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 7.6.0"
},
"package": {
"ecosystem": "Maven",
"name": "com.github.junrar:junrar"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "7.6.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-86071"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-17T16:30:46Z",
"nvd_published_at": "2026-09-16T19:17:58Z",
"severity": "LOW"
},
"details": "## Summary\n\n`LocalFolderExtractor` validates only the final canonical file path before extraction. However, `makeFile()` creates intermediate directories one path segment at a time without checking whether each created directory remains inside the destination folder.\n\nA malicious RAR entry can make the final file path resolve inside the extraction destination, while causing intermediate `mkdir()` calls to create attacker-chosen directories outside the extraction root.\n\nThis is an extraction root escape via unchecked intermediate directory creation. The default impact is directory creation outside the intended destination, not unconditional arbitrary file content write.\n\n## Affected Code\n\n- `src/main/java/com/github/junrar/LocalFolderExtractor.java`\n - `createFile()` checks only the final canonical path.\n - `makeFile()` calls `dir.mkdir()` for each intermediate segment without containment checks.\n\nRelevant code flow:\n\n```java\nprivate File createFile(final FileHeader fh, final File destination) throws IOException {\n String name = invariantSeparatorsPathString(fh.getFileName());\n File f = new File(destination, name);\n String dirCanonPath = f.getCanonicalPath();\n if (!dirCanonPath.startsWith(destination.getCanonicalPath() + File.separator)) {\n throw new IllegalStateException(...);\n }\n if (!f.exists()) {\n f = makeFile(destination, name);\n }\n return f;\n}\n\nprivate File makeFile(final File destination, final String name) throws IOException {\n final String[] dirs = name.split(\"/\");\n String path = \"\";\n for (int i = 0; i \u003c dirs.length - 1; i++) {\n path = path + File.separator + dirs[i];\n File dir = new File(destination, path);\n dir.mkdir();\n }\n path = path + File.separator + dirs[dirs.length - 1];\n final File f = new File(destination, path);\n f.createNewFile();\n return f;\n}\n```\n\n## Impact\n\nAn attacker who can supply a malicious RAR archive can create directories outside the intended extraction directory.\n\nThis violates the expected extraction boundary and can be used for filesystem pollution or file-vs-directory squatting. For example, an attacker can create a directory at a path where a later security-sensitive file is expected, causing future writes to that path to fail.",
"id": "GHSA-89m4-43j5-vhhx",
"modified": "2026-09-17T16:30:46Z",
"published": "2026-09-17T16:30:46Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/junrar/junrar/security/advisories/GHSA-89m4-43j5-vhhx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86071"
},
{
"type": "WEB",
"url": "https://github.com/junrar/junrar/commit/e6e333b195a1e3ad271a18fd79d8ac1eb5289343"
},
{
"type": "PACKAGE",
"url": "https://github.com/junrar/junrar"
},
{
"type": "WEB",
"url": "https://github.com/junrar/junrar/releases/tag/v7.6.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Junrar: LocalFolderExtractor mkdir escape allows directory creation outside extraction root"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.