Skip to content

AAK-MCP-FROMOPENAPI-CVE-2026-115750-001: mcp-from-openapi from 2.2.0 below 2.9.0: spec credentials follow a cross-origin redirect, and a trailing dot slips past blockedHosts

Severity
LOW
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
McpFromOpenapiRedirectCredentialLeak

What it detects

mcp-from-openapi (npm; agentfront/mcp-from-openapi) builds MCP tools from an OpenAPI spec it fetches with fromURL(). Two flaws are fixed in 2.9.0. CVE-2026-115750 (2.5.0 to 2.8.x): safeFetch() carries the caller's Authorization and Cookie headers to another origin when the spec host redirects there, so a spec host or an open redirect can send the request to an attacker's origin and collect bearer tokens or cookies. CVE-2026-115751 (2.2.0 to 2.8.x): a hostname with a trailing dot (blocked.example.invalid.) is not matched against ssrf.blockedHosts, so a spec URL or redirect target reaches a host the operator blocked (CVSS 3.1 3.7 each, CWE-522/CWE-184, GHSA-ff5q-5r4v-fw4v). 2.9.0 keeps caller headers on their origin and normalizes hostnames before every host-list check.

How to fix

Upgrade mcp-from-openapi to 2.9.0 or later and pin it. Until then pass no credentials to spec fetches from hosts you do not control, and list the trailing-dot form of each blocked host in ssrf.blockedHosts as well.

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

agent-audit-kit scan . --rules AAK-MCP-FROMOPENAPI-CVE-2026-115750-001

Limitations

Reports mcp-from-openapi from 2.2.0 below 2.9.0 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. 2.2.0 to 2.4.x carry only CVE-2026-115751: safeFetch(), and with it the redirect leak, first ships in 2.5.0. latest was 2.9.1 on 2026-10-24 and states no version, so an unversioned reference is not reported. Releases below 2.5.0 also fire AAK-MCP-FROMOPENAPI-CVE-2026-59973-001. PyPI's mcp-from-openapi is another project and is not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

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-FROMOPENAPI-CVE-2026-115750-001.md: the page then shows that text, with the registry reference appended under it.