CVE-2026-52776
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 35% of all known CVEs.
References
Related Vulnerabilities
Other CWE-184 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-5217 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-43396 | High | 8.8 | 55% | - | Fix |
| CVE-2017-7525 | Critical | 9.8 | 38% | - | Fix |
| CVE-2024-5178 | Medium | 4.9 | 34% | - | - |
| CVE-2018-7489 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-6383 | High | 8.8 | 13% | - | - |
Common questions
How do I fix CVE-2026-52776?
No published fix for CVE-2026-52776 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-52776 being actively exploited?
Not that we know of. CVE-2026-52776 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.42% is the estimated probability that it will be exploited in the next 30 days. That is higher than 35% of all scored CVEs.
How severe is CVE-2026-52776?
CVE-2026-52776 has a CVSS v4 base score of 8.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-52776
Markdown
[](https://tridentstack.com/cve/CVE-2026-52776)HTML
<a href="https://tridentstack.com/cve/CVE-2026-52776"><img src="https://tridentstack.com/cve/badge/CVE-2026-52776.svg" alt="CVE-2026-52776"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.