CVE-2026-115751 mcp-from-openapi 2.2.0 before 2.9.0 SSRF blockedHosts Bypass via Trailing-Dot Hostname
Medium 6.3
Published
Updated
Check this codebase for CVE-2026-115751 and fix it if it is affected.
What it is: CVE-2026-115751 is a medium-severity vulnerability in agentfront mcp-from-openapi, published on 23 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115751 exists.
Affected product: agentfront mcp-from-openapi. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-115751/ (Markdown: https://insights.sbomify.com/CVE-2026-115751/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115751?
CVE-2026-115751 is a medium-severity vulnerability in agentfront mcp-from-openapi, published on 23 Oct 2026.
Official description
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.
Weakness: CWE-184
Which versions are affected by CVE-2026-115751?
How do I fix CVE-2026-115751?
No fix has been published for CVE-2026-115751 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115751 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115751 exists.
Sources
Also known as GHSA-wfcf-h98w-gp9m.