CVE-2026-115751 agentfront CVE debrief

Who should care

Defenders and security teams using mcp-from-openapi versions 2.2.0 before 2.9.0 should assess exposure and prioritize updates to mitigate the risks associated with this vulnerability. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

The vulnerability in mcp-from-openapi allows for SSRF attacks, enabling attackers to bypass security controls and potentially access sensitive information or compromise internal systems.

• Potential SSRF attacks on internal hosts
• Bypassing of ssrf.blockedHosts denylist
• Exposure of sensitive information
• Compromise of internal systems

Technical summary

The mcp-from-openapi library is vulnerable to SSRF attacks, allowing attackers to bypass the ssrf.blockedHosts denylist by appending a trailing dot to blocked hostnames. This vulnerability can be exploited by attackers who control an OpenAPI spec URL or redirect target, potentially leading to access to sensitive information or compromise of internal systems. Defenders should prioritize verifying and updating mcp-from-openapi to version 2.9.0 or later, and assess exposure in their environments to mitigate these risks.

Defensive priority

Defenders should prioritize verifying and updating mcp-from-openapi to version 2.9.0 or later, and assess exposure in their environments.

Recommended defensive actions

• Verify and update mcp-from-openapi to version 2.9.0 or later
• Assess exposure in environments using affected versions
• Monitor for potential SSRF attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and potential attack vectors. The vulnerability allows for SSRF attacks, enabling attackers to bypass security controls and potentially access sensitive information or compromise internal systems. The source item and CVE record confirm the affected versions and provide additional context for defenders.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.