CVE-2026-46345
Description
A flaw was found in compliance-trestle. The trestle author jinja command, when processing the -o/--output argument, is vulnerable to path traversal. This allows a local attacker to write files to arbitrary locations outside the intended workspace by providing specially crafted path sequences or absolute paths, potentially leading to unauthorized modification of system files or data.
Statement
An IMPORTANT impact path traversal flaw was found in compliance-trestle, a compliance-as-code framework that Red Hat uses only as a build-time dependency when generating compliance content. The trestle author jinja command does not properly validate the -o/--output argument for ../, ..\, or absolute path sequences, allowing a local attacker who controls that argument to write files to arbitrary locations outside the intended workspace, potentially resulting in unauthorized modification of system files or data. Red Hat rated this flaw IMPORTANT (CVSS 8.4, CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which matches the upstream CVSS rating, so there is no meaningful severity difference. The two Red Hat product streams that reference compliance-trestle, the File Integrity Operator's openshift-compliance-content-rhel8 content image and the Red Hat Hardened Images scap-security-guide package, are DELEGATED; the responsible business units determined that the vulnerable component is not present in the shipped products (delegated resolution NOTAFFECTED), so no Red Hat product is known to be exposed to this flaw at runtime.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.4 | N/A | 8.4 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
