Out-of-directory extraction via unsafe archive component stripping
Published Jan 20, 2026 · Updated Jan 20, 2026
Path traversal in jaraco.context 5.2.0 through 6.0.2 allows remote attackers to extract files outside the intended directory. The tarball() helper passes archive entries through strip_first_component, which removes only the leading directory and preserves ../ sequences before extraction. Exploitation requires a consuming application to invoke tarball() on an attacker-controlled archive; nested archives can repeat the traversal across extraction boundaries.
Summary
What happened
Path traversal in jaraco.context 5.2.0 through 6.0.2 allows remote attackers to extract files outside the intended directory. The tarball() helper passes archive entries through strip_first_component, which removes only the leading directory and preserves ../ sequences before extraction. Exploitation requires a consuming application to invoke tarball() on an attacker-controlled archive; nested archives can repeat the traversal across extraction boundaries.
The record
- CVE
- CVE-2026-23949
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- jaraco
- Product
- jaraco.context
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.2.0, < 6.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted tar-path proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo