Path Traversal in compliance-trestle (CVE-2026-45774)
Summary
Path traversal in compliance-trestle (CVE-2026-45774). Risk of unauthorized operations or information disclosure. Exploitable via trestle_root. Mitigation: upgrade to 3.12.2 or later.
Original description
The description as published by the source.
compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the compliance-trestle library's profile import mechanism resolves trestle:// URIs and relative file paths by joining them with trestle_root and calling .resolve(), but performs no boundary check to ensure the resolved path stays within the trestle workspace. An attacker can craft a malicious OSCAL profile YAML with imports[].href containing path traversal sequences to read arbitrary files from the server filesystem. Versions 3.12.3 and 4.0.3 patch the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45774 has been found in compliance-trestle.
Attackers can target a specific entry point like trestle_root over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade compliance-trestle to 3.12.2 or later.
If unsure, ask your IT team or search "compliance-trestle CVE-2026-45774" on the vendor's site.
CVE-2026-45774 (compliance-trestle) — CWE-22
Attack surface: trestle_root / TRESTLE_HREF_REGEX
Patched: 3.12.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in compliance-trestle. Attackers reach the vulnerable code path via trestle_root.
Check the vendor advisory for the affected versions of compliance-trestle. Attack surface: trestle_root / TRESTLE_HREF_REGEX.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.12.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'compliance-trestle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'compliance-trestle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
compliance-trestleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade compliance-trestle to 3.12.2ステージング環境で 3.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com