Live › vulnerability › CVE-2026-115750
Go to dashboardmcp-from-openapi versions 2.5.0 through 2.8.x forward Authorization and Cookie headers when its safeFetch() follows a redirect to a different origin. An attacker who controls the OpenAPI spec host, or can abuse an open redirect on it, can capture bearer tokens or cookies.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that call fromURL() with credentials to load an OpenAPI spec from a remote host they do not fully control, or from a host with an open redirect. Projects that only load local spec files or use no auth headers when fetching specs can skip it.
No product ranges from the sources yet.
mcp-from-openapi in the project lockfile or with npm ls mcp-from-openapifromURL() that load specs from remote hosts with credentials set in headersmcp-from-openapi to 2.9.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
mcp-from-openapi from 2.5.0 before 2.9.0 contains a credential exposure vulnerability that allows attackers to capture Authorization and Cookie headers because safeFetch() forwards them on cross-origin redirects. Attackers controlling a spec host or abusing an open redirect can redirect fromURL() spec requests to their own origin to steal bearer tokens or cookies.
This page as .md · .json · in your agent: get_signal("CVE-2026-115750")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.