CVE-2026-73030
Description
A flaw was found in unearth. This path traversal vulnerability exists in the is_within_directory function, which fails to normalize paths before validation. This allows ../ sequences to bypass directory containment checks. An attacker can exploit this by supplying malicious tar archives with symlink members or traversal sequences, leading to the ability to write files to arbitrary filesystem locations accessible to the process.
Statement
A flaw was found in the unearth Python package, which ships as a dependency in the Konflux mintmaker-renovate-image container image. The is_within_directory function fails to normalize paths before validation, allowing ../ sequences in archive member names to bypass directory containment checks. An attacker who supplies a malicious tar archive containing symlink members or path traversal sequences can cause files to be written to arbitrary filesystem locations accessible to the process, resulting in a high impact to integrity and availability with no direct impact on confidentiality. Red Hat rates this flaw as IMPORTANT (CVSS 8.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H); exploitation requires a victim to process an attacker-supplied archive. Within Red Hat, only the Konflux mintmaker-renovate-image container, which includes the vulnerable unearth dependency, is in scope, and a fix is being pursued through the responsible Konflux component team via the delegated resolution process.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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.
