CVE-2026-46380
Received Received - Intake

SSRF Vulnerability in compliance-trestle HTTPSFetcher

Publication date: 2026-08-14

Last updated on: 2026-08-14

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-14
Last Modified
2026-08-14
Generated
2026-08-14
AI Q&A
2026-08-14
EPSS Evaluated
N/A
NVD
CVE-2026-46380
EUVD
EUVD-2026-58712

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
oscal-compass compliance-trestle to 4.0.3 (exc)
oscal-compass compliance-trestle From 0.0.2 (inc) to 4.0.2 (inc)
oscal-compass compliance-trestle to 3.3.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in compliance-trestle versions before 3.12.2 and 4.0.3. The HTTPSFetcher._do_fetch() method passes user-supplied URLs directly to requests.get() without validation, allowing attackers to trick the system into making unauthorized requests to internal services or cloud metadata endpoints.

Detection Guidance

To detect this vulnerability, monitor network traffic for unexpected outbound requests to internal or cloud metadata endpoints. Check logs for requests to IP ranges like 169.254.169.254 or private IPs (RFC 1918). Use tools like tcpdump or Wireshark to inspect traffic from compliance-trestle processes.

Impact Analysis

An attacker could exploit this to access internal resources, steal sensitive cloud credentials, or compromise CI/CD environments. The vulnerability requires low privileges and some user interaction but can lead to high confidentiality loss.

Mitigation Strategies
  • Upgrade compliance-trestle to versions 3.12.2 or 4.0.3 or later to address the SSRF vulnerability.
  • Configure environment variables like TRESTLE_BLOCK_PRIVATE_IPS to block private IP ranges in production.
  • Implement domain allowlisting for URLs fetched by compliance-trestle to restrict access.
  • Review and restrict network access for compliance-trestle processes to limit potential SSRF impact.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46380. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart