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.
CVE-2026-46380
This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.7
- EG Score
- 6.7(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity67% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
August 17, 2026
Advisory Details (4)
Auto-updated Aug 14, 2026advisory-database/vulns/compliance-trestle/PYSEC-2026-2427.yaml at main · pypa/advisory-database · GitHub
https://github.com/pypa/advisory-database/tree/main/vulns/compliance-trestle/PYSEC-2026-2427.yamlcommit 5c65c5926fe7 (oscal-compass/compliance-trestle)
Fix landed in oscal-compass/compliance-trestle commit 5c65c5926fe7 — awaiting tagged release
https://github.com/oscal-compass/compliance-trestle/commit/5c65c5926fe7ca908b9c1d281f904e7d97ba8310commit 53de5e753328 (oscal-compass/compliance-trestle)
Fix landed in oscal-compass/compliance-trestle commit 53de5e753328 — awaiting tagged release
https://github.com/oscal-compass/compliance-trestle/commit/53de5e75332888ea54f5da41d4c7859bb1d608e1Critical SSRF (CWE-918) · Advisory · oscal-compass/compliance-trestle · GitHub
https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-w76h-q7c6-jpjpVendor Advisories for CVE-2026-46380(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| compliance-trestle | 0.0.2 ... 4.0.2 (100 versions) | 4.0.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:39 UTCEG score recompute
- 2026-08-23 14:27 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:24 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 10:43 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:31 UTCEG score recompute
- 2026-08-17 19:50 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:57 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:33 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-14 17:44 UTCEG score recompute
Show 7 moreShow fewer
- 2026-07-31 06:18 UTCEG score recompute
- 2026-07-27 09:36 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-28 19:06 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-46380?
When was CVE-2026-46380 disclosed?
Is CVE-2026-46380 actively exploited?
What is the CVSS score of CVE-2026-46380?
How do I remediate CVE-2026-46380?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46380
Is Your Infrastructure Affected by CVE-2026-46380?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.