CVE-2026-46380

MEDIUMPre-NVD 6.76.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.7
EG Score
6.7MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity67% × 45%
Impact severity (EG Severity): CVSS 6.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.7): severity, escalated by confirmed exploitation. This CVE's 6.7 is its impact severity (EG Severity), not escalated.

EG Severity
6.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 28, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available. Sources: github, github_commit.
Web page

advisory-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.yaml
GitHub commit

commit 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/5c65c5926fe7ca908b9c1d281f904e7d97ba8310
GitHub commit

commit 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/53de5e75332888ea54f5da41d4c7859bb1d608e1
GitHub advisoryMentions a patch (unverified)

Critical SSRF (CWE-918) · Advisory · oscal-compass/compliance-trestle · GitHub

https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-w76h-q7c6-jpjp

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
compliance-trestle0.0.2 ... 4.0.2 (100 versions)
  • 4.0.0 up to 4.0.3: fixed in 4.0.3
  • every version up to 3.12.2: fixed in 3.12.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-18 03:37 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-12 16:03 UTCEG score recompute
  11. 2026-10-11 19:45 UTCEG score recompute
  12. 2026-10-11 17:00 UTCEG score recompute
  13. 2026-10-11 14:25 UTCEG score recompute
  14. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-08 14:54 UTCOSV refresh
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 51 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-18 20:36 UTCEG score recompute
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-09-14 06:39 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  13. 2026-09-13 02:09 UTCOSV refresh
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  15. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  17. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  24. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  25. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  26. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  27. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  28. 2026-08-25 04:39 UTCEG score recompute
  29. 2026-08-23 14:27 UTCEG score recompute
  30. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-08-21 15:24 UTCEG score recompute
  33. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-08-20 10:43 UTCEG score recompute
  35. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  36. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-17 20:31 UTCEG score recompute
  38. 2026-08-17 19:50 UTCEG score recompute
  39. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  40. 2026-08-17 07:57 UTCEG score recompute
  41. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-08-16 02:33 UTCEG score recompute
  43. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-08-14 17:44 UTCEG score recompute
  45. 2026-07-31 06:18 UTCEG score recompute
  46. 2026-07-27 09:36 UTCEG score recompute
  47. 2026-07-23 03:17 UTCEG score recompute
  48. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 1st percentile
  49. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 1st percentile
  50. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 1st percentile
  51. 2026-05-28 19:06 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46380?
CVE-2026-46380 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the HTTPSFetcher.dofetch() method passes a user-supplied URL directly to requests.get() without validation. This allows an attacker to perform Server-Side Request Forgery, targeting…
When was the CVE record for CVE-2026-46380 published?
The CVE record for CVE-2026-46380 was published on May 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-46380 actively exploited?
CVE-2026-46380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46380?
CVE-2026-46380 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46380?
A fix for CVE-2026-46380 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46380 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46380

Explore →

Is Your Infrastructure Affected by CVE-2026-46380?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs