CVE-2026-52776

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Compliance-trestle (Trestle) is a tooling platform for managing compliance as code. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, the URLSecurityValidator that guards trestle's remote-fetch paths against server-side request forgery can be bypassed to reach loopback, link-local, cloud-metadata, and internal network endpoints it was designed to block. The blocklist does not canonicalize IPv4-mapped IPv6 literals such as [::ffff:169.254.169.254], which resolve to IPv6Address objects that never match the blocked IPv4 ranges, and it does not block the unspecified address 0.0.0.0, which routes to local services on Linux and inside containers. An attacker who can supply or influence an OSCAL artifact that trestle fetches, such as a malicious profile whose imports reference one of these bypass URLs, can cause the HTTPSFetcher and SFTPFetcher paths to contact cloud instance-metadata services, loopback interfaces, or internal hosts. This issue is fixed in versions 3.12.4 and 4.1.0.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/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 computed
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit d107cd16efe8 (oscal-compass/compliance-trestle)

Fix landed in oscal-compass/compliance-trestle commit d107cd16efe8 — awaiting tagged release

https://github.com/oscal-compass/compliance-trestle/commit/d107cd16efe8eb15d46be3c1d97f1ec73d32447c
github_commit

commit 5335ff873a2a (oscal-compass/compliance-trestle)

Fix landed in oscal-compass/compliance-trestle commit 5335ff873a2a — awaiting tagged release

https://github.com/oscal-compass/compliance-trestle/commit/5335ff873a2a68eb7de43df029bea09cadff22fd
github Patch Available🟡 PoC Available

compliance-trestle URLSecurityValidator SSRF allowlist bypass via IPv4-mapped IPv6 and 0.0.0.0 · Advisory · oscal-compass/compliance-trestle · GitHub

https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-h47f-gmjp-m7rr

Vendor Advisories for CVE-2026-52776(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 rangeFixed inDependents
compliance-trestle0.0.2 ... 4.0.3 (104 versions)4.1.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 43× 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.

  1. 2026-09-18 22:43 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:32 UTCEG score recompute
  4. 2026-09-17 00:22 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 12:17 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 13:13 UTCEG score recompute
  9. 2026-09-14 00:59 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 15:53 UTCEG score recompute
  12. 2026-09-11 17:49 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 19:45 UTCEG score recompute
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-09 05:16 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:44 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 22:25 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-06 00:14 UTCEG score recompute
  23. 2026-09-04 14:26 UTCEG score recompute
  24. 2026-09-04 05:06 UTCEPSS rescore
  25. 2026-09-02 23:38 UTCEG score recompute
Show 19 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 22:47 UTCEG score recompute
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 11:45 UTCEG score recompute
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-31 05:59 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 07:55 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 08:38 UTCEG score recompute
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 01:17 UTCEG score recompute
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 16:04 UTCEG score recompute
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 14:45 UTCEG score recompute
  17. 2026-08-25 23:25 UTCEG score recompute▲ 8.60
  18. 2026-08-25 23:24 UTCMITRE cvelistV5CVSS v3 → 8.6 · CVSS v4 → 8.6
  19. 2026-08-12 16:21 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52776?
CVE-2026-52776 is a high vulnerability published on August 12, 2026. Compliance-trestle (Trestle) is a tooling platform for managing compliance as code. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, the URLSecurityValidator that guards trestle's remote-fetch paths against server-side request forgery can be bypassed to reach loopback, link-local,…
When was CVE-2026-52776 disclosed?
CVE-2026-52776 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52776 actively exploited?
CVE-2026-52776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-52776?
CVE-2026-52776 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-52776?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52776, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-52776?

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

Start Free Scan →Browse All CVEs