Skip to content

AAK-MCP-TRAWL-CVE-2026-122140-001: Trawl image 1.5.0 to 1.9.3: IPv4-mapped IPv6 addresses and DNS rebinding pass the MCP outbound URL policy

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
TrawlMcpOutboundPolicyMappedIpv6Ssrf

What it detects

Trawl (germondai/trawl), a self-hosted scraping engine with an optional MCP endpoint (MCP_ENABLED=true, Streamable HTTP at /mcp), ships as the image ghcr.io/germondai/trawl. From 1.5.0 its MCP tools check each target and redirect against an outbound policy meant to keep them off loopback, private and metadata addresses, but isPrivateIp recognised an IPv4-mapped IPv6 address only in dotted form, and the URL parser rewrites every mapped literal into hex (::ffff:7f00:1) first, so an unauthenticated MCP caller, directly or through a redirect, could fetch loopback, private and cloud-metadata services and read the response (CVE-2026-122140, CVSS 3.1 5.8, CWE-918, GHSA-mj45-84p2-v77q). The same releases checked a hostname's DNS answers apart from the connection that used them, so a name that rebinds from a public to a private address between the two passed as well (GHSA-7qmf-c45g-5p4q, no CVE id, rated moderate by the maintainer, CWE-367). Checked in the source at the commit each image's label names: 1.4.2 has neither the MCP routes nor apps/api/src/outbound-policy.ts; 1.5.0 adds both, with the dotted-only match and a validator that resolves the name and hands back only the URL, which the fetch resolves again, and the file is unchanged at 1.9.3; 1.10.0 classifies addresses numerically with Node's BlockList and pins each guarded connection to the validated address (apps/api/src/public-egress.ts, 17cdb33a, #263).

How to fix

Run ghcr.io/germondai/trawl 1.10.0 or later, pinned by version. Until then leave MCP_ENABLED off, or keep the MCP endpoint off any network an untrusted caller reaches, and run the container where loopback, private and metadata addresses hold nothing to read.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-TRAWL-CVE-2026-122140-001

Limitations

Reads image references only: an image: value or any other mention of ghcr.io/germondai/trawl:TAG in YAML (compose files, Kubernetes manifests, MCP configs), a Helm values mapping of repository and tag, Dockerfile and Containerfile FROM, and docker run arguments in *mcp*.json and claude_desktop_config.json. Tags from 1.5.0 below 1.10.0 are reported, with the -baseline and -fonts builds; tags below 1.5.0 predate the MCP endpoint and are not. latest was the 1.11.0 image on 2026-11-11, so an untagged reference is not reported. latest-fonts is still the 1.6.0 image, affected, but states no version, so it is not reported, nor are the nightly- and sha- tags. The rule reads the tag, not whether MCP_ENABLED is set, so a deployment with MCP off is reported too. A server built from source states no version AAK reads, and npm's and PyPI's trawl are other projects. Mirrors under another registry are not matched, and commented-out lines are skipped.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-TRAWL-CVE-2026-122140-001.md: the page then shows that text, with the registry reference appended under it.