Live › vulnerability › CVE-2026-115751
Go to dashboardmcp-from-openapi, a tool that turns OpenAPI specs into MCP servers, has a server-side request forgery flaw in versions 2.2.0 before 2.9.0. An attacker who controls an OpenAPI spec URL or a redirect target can append a trailing dot to a blocked hostname to make the server fetch content from hosts the operator meant to block.
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 run mcp-from-openapi at a version from 2.2.0 up to but not including 2.9.0 and that use the ssrf.blockedHosts denylist to keep the server away from internal hosts are exposed. The risk applies when attackers can supply the OpenAPI spec URL or influence a redirect target. Deployments that only load trusted, fixed specs can deprioritize it.
No product ranges from the sources yet.
mcp-from-openapi in each project's lockfile or package.json, looking for versions from 2.2.0 up to but not including 2.9.0.ssrf.blockedHosts setting in your configuration to see whether you rely on the denylist.mcp-from-openapi to 2.9.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Agentfront mcp-from-openapi from 2.2.0 before 2.9.0 contains a server-side request forgery vulnerability that allows attackers to bypass the ssrf.blockedHosts denylist using trailing-dot hostnames. Attackers who control an OpenAPI spec URL or redirect target can append a root dot to a blocked hostname to fetch content from operator-blocked hosts.
This page as .md · .json · in your agent: get_signal("CVE-2026-115751")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.