SSRF (Server-Side Request Forgery) in compliance-trestle (CVE-2026-46380)
Summary
SSRF in compliance-trestle (CVE-2026-46380). Confidential information can be exposed externally. Mitigation: upgrade to 3.12.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46380 has been found in compliance-trestle.
Confidential information can be exposed externally. CVSS score: 6.7/10.
What to do: upgrade compliance-trestle to 3.12.2 or later.
If unsure, ask your IT team or search "compliance-trestle CVE-2026-46380" on the vendor's site.
CVE-2026-46380 (compliance-trestle) — CWE-918 / CVSS v3 6.7
Attack vector: local
Patched: 3.12.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in compliance-trestle.
Check the vendor advisory for the affected versions of compliance-trestle.
Severity: Medium (CVSS 6.7/10). Confidential information can be exposed externally.
Update to 3.12.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'compliance-trestle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'compliance-trestle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
compliance-trestleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade compliance-trestle to 3.12.2ステージング環境で 3.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com