CVE-2026-122140

Received Received - Intake

Server-Side Request Forgery in Trawl 1.5.0 to 1.10.0

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: VulnCheck

Description

Trawl 1.5.0 before 1.10.0 contains a server-side request forgery vulnerability that allows unauthenticated attackers to bypass the MCP outbound URL policy using IPv4-mapped IPv6 addresses. Attackers can supply hex-normalized addresses like ::ffff:7f00:1 directly or via redirects to fetch loopback, private, and cloud metadata services and read responses.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-11-04

Last Modified

2026-11-04

Generated

2026-11-05

AI Q&A

2026-11-05

EPSS Evaluated

N/A

NVD

CVE-2026-122140

EUVD

EUVD-2026-117094

Affected Vendors & Products

Vendor	Product	Version / Range
germondai	trawl	1.5.0

Helpful Resources

Exploitability

CWE

KEV

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

Executive Summary

CVE-2026-122140 is a server-side request forgery (SSRF) vulnerability in Trawl versions 1.5.0 through 1.9.3. It allows unauthenticated attackers to bypass the MCP outbound URL policy by using IPv4-mapped IPv6 addresses like ::ffff:7f00:1. This lets attackers send requests to loopback, private, or cloud metadata services and read sensitive responses.

Detection Guidance

To detect this vulnerability, check if your Trawl instance is running a vulnerable version (1.5.0 to 1.9.3). Inspect network logs for requests using IPv4-mapped IPv6 addresses like ::ffff:7f00:1 targeting loopback or private addresses. Use commands like `curl -v http://localhost:PORT/admin/mcp/status` to verify MCP session configurations and ensure publicOnly: true is enforced.

Impact Analysis

If you use Trawl with MCP enabled, attackers could exploit this to access internal services, read sensitive data, or interact with cloud metadata services. This could lead to data breaches, unauthorized access, or further network compromise. The impact depends on your deployment and whether MCP is enabled.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles or HIPAA's security requirements for protected health information. Organizations using affected Trawl versions may face compliance violations if exploited.

Mitigation Strategies

Upgrade Trawl to version 1.10.0 or later immediately. Disable MCP if not required by setting MCP_ENABLED=false. Recreate MCP sessions with publicOnly: true. Ensure your outbound URL policy enforces numeric subnet checks for IPv4-mapped IPv6 addresses. Review and update proxy configurations to reject Trawl's intercepting MITM upstream.

Hi! I’m here to help you understand CVE-2026-122140. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...