CVE-2026-23949
Description
A flaw was found in jaraco.context. The jaraco.context.tarball() function is vulnerable to a Zip Slip path traversal when processing malicious tar archives. A remote attacker can exploit this by crafting a specially designed tar file, which, when extracted, allows files to be written outside the intended directory. This could lead to arbitrary file overwrites or information disclosure on the system.
Statement
This vulnerability is rated Important for Red Hat products that utilize jaraco.context versions prior to 6.1.0 and process untrusted tar archives. A path traversal flaw in the jaraco.context.tarball() function allows attackers to extract files outside the intended directory due to improper handling of ../ sequences, including in nested tarballs. This could lead to arbitrary file write.
Mitigation
The vulnerability arises from processing untrusted tar archives. To mitigate the risk, Red Hat recommends avoiding the processing of tar archives from untrusted sources. If processing untrusted archives is unavoidable, ensure that the environment where `jaraco.context.tarball()` is used is isolated and has minimal privileges.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
