# compliance-trestle Vulnerable to SSRF in Remote Fetching Subsystem

Advisory record · `GHSA-w76h-q7c6-jpjp`

- **Identifiers:** `GHSA-w76h-q7c6-jpjp` · `CVE-2026-46380` · `PYSEC-2026-2427`
- **State:** Confirmed
- **Severity:** CVSS 6.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 28 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2026, 18:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `compliance-trestle` (PyPI): affected `>=4.0.0, <4.0.3 || <3.12.2`; fixed in `4.0.3`, `3.12.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> compliance-trestle before 3.12.2, and 4.0.0 through 4.0.2, is vulnerable to server-side request forgery in its remote fetching subsystem. Unvalidated user-supplied URLs let an attacker make the server reach internal services or cloud metadata endpoints. Upgrade to 3.12.2 or 4.0.3.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.7 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w76h-q7c6-jpjp)

## Sources

- [GitHub Advisory Database: GHSA-w76h-q7c6-jpjp](https://github.com/advisories/GHSA-w76h-q7c6-jpjp)
- [OSV: GHSA-w76h-q7c6-jpjp](https://osv.dev/vulnerability/GHSA-w76h-q7c6-jpjp)
- <https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-w76h-q7c6-jpjp>
- <https://github.com/oscal-compass/compliance-trestle/commit/53de5e75332888ea54f5da41d4c7859bb1d608e1>
- <https://github.com/oscal-compass/compliance-trestle/commit/5c65c5926fe7ca908b9c1d281f904e7d97ba8310>
- <https://github.com/oscal-compass/compliance-trestle>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-w76h-q7c6-jpjp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w76h-q7c6-jpjp/>. Everything for agents: <https://agentprime.io/llms.txt>.