GHSA-89m4-43j5-vhhx: Path Traversal

Published Sep 17, 2026
·
Updated

Summary

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.java - createFile() checks only the final canonical path. - makeFile() calls dir.mkdir() for each intermediate segment without containment checks.

Relevant code flow:

java 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 Software

1 affected componentFixes available
maven/com.github.junrar:junrar<=7.6.0
7.6.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/com.github.junrar:junrar to a version that resolves this vulnerability.

    Fixed in 7.6.1

Event History

Sep 17, 2026
Advisory Published
via GitHub·04:30 PM
Data Sourced
via GitHub·04:30 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed?

Deployments that use junrar's LocalFolderExtractor to extract attacker-controlled RAR archives are exposed. The affected code is in src/main/java/com/github/junrar/LocalFolderExtractor.java.

2

What does an attacker need to exploit this issue?

An attacker needs to supply a malicious RAR entry whose path causes intermediate directory creation outside the extraction destination while the final canonical file path still resolves inside that destination. No privileges or user interaction are required according to the provided severity vector.

3

What is the practical impact of a successful exploit?

The default impact is creation of attacker-chosen directories outside the intended extraction root. The provided information does not describe this as an unconditional arbitrary file-content write.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203