{"answers":{"affected":"3 open source packages ship an affected version, including compliance-trestle.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52776 exists.","fix":"Upgrade compliance-trestle to 4.1.0 or later.","what":"CVE-2026-52776 is a high-severity server-side request forgery vulnerability in oscal-compass compliance-trestle, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52776 and fix it if it is affected.\n\nWhat it is: CVE-2026-52776 is a high-severity server-side request forgery vulnerability in oscal-compass compliance-trestle, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52776 exists.\n\nAffected packages and fixed versions:\n- compliance-trestle (PyPI): affected all versions; fixed in 4.1.0\n- compliance-trestle (PyPI): affected all versions; fixed in 4.1.0\n- compliance-trestle (PyPI): affected all versions; fixed in 4.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-52776/ (Markdown: https://insights.sbomify.com/CVE-2026-52776/index.md)","id":"CVE-2026-52776","markdown":"https://insights.sbomify.com/CVE-2026-52776/index.md","name":"CVE-2026-52776","record":{"aliases":["GHSA-h47f-gmjp-m7rr","PYSEC-2026-3659"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Compliance as Code tool","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in Trestle to access internal network resources and cloud metadata via crafted IPv6 or unspecified addresses.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Trestle URLSecurityValidator SSRF allowlist bypass via IPv4-mapped IPv6 and 0.0.0.0","id":"CVE-2026-52776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"YesWiki: Authenticated PHP Object Injection in BazarImportAction via unserialize","id":"CVE-2026-52777"},"packages":[{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"compliance-trestle","purl":null,"source":"GHSA-h47f-gmjp-m7rr"},{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"compliance-trestle","purl":"pkg:pypi/compliance-trestle","source":"GHSA-h47f-gmjp-m7rr"},{"ecosystem":"PyPI","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"compliance-trestle","purl":"pkg:pypi/compliance-trestle","source":"PYSEC-2026-3659"}],"prev":{"headline":"YesWiki Authenticated SQL Injection in ReactionManager","id":"CVE-2026-52775"},"products":["compliance-trestle"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["oscal-compass"]},"summary":"Attackers can bypass SSRF protections in Trestle to access internal network resources and cloud metadata via crafted IPv6 or unspecified addresses.","url":"https://insights.sbomify.com/CVE-2026-52776/"}