CVE-2026-46380PYSEC-2026-2427GHSA-W76H-Q7C6-JPJP
compliance-trestle Vulnerable to SSRF in Remote Fetching Subsystem
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.3, 3.12.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the HTTPSFetcher._do_fetch() method passes a user-supplied URL directly to requests.get() without validation. This allows an attacker to perform Server-Side Request Forgery, targeting internal services or cloud metadata endpoints. Versions 3.12.2 and 4.0.3 fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- oscal-compass compliance-trestle
From 4.0.0 · fixed in 4.0.3; fixed in 3.12.2
- compliance-trestlePyPI
fixed in 3.12.2; From 4.0.0 · fixed in 4.0.3
- compliance-trestlePyPI
From 4.0.0 · fixed in 4.0.3
- compliance-trestlePyPI
fixed in 3.12.2