---
title: "CVE-2026-59973: FrontMCP - Server Side Request Forgery"
description: "FrontMCP mcp-from-openapi 2.3.0 to 2.5.0 and frontmcp & @frontmcp/adapters 1.2.1 to 1.5.0 contain a server-side request forgery caused by improper validation of external $ref URLs in OpenAPI specs, letting authenticated users access internal network services, exploit requires authenticated user able to import or configure OpenAPI specs."
url: https://panop.io/threat-heartbeat/CVE-2026-59973/
---

# CVE-2026-59973 FrontMCP - Server Side Request Forgery

FrontMCP mcp-from-openapi 2.3.0 to 2.5.0 and frontmcp & @frontmcp/adapters 1.2.1 to 1.5.0 contain a server-side request forgery caused by improper validation of external $ref URLs in OpenAPI specs, letting authenticated users access internal network services, exploit requires authenticated user able to import or configure OpenAPI specs.

CVSS base score 8.5 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.39% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-59973)

## Details

Type

Server Side Request Forgery

Impact

Server Side Request Forgery, Information Disclosure

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Published

15 September 2026

Updated

15 October 2026

Weakness

[CWE-918](https://cwe.mitre.org/data/definitions/918.html)

## Vendor fix

Update to mcp-from-openapi 2.5.0 and frontmcp & @frontmcp/adapters 1.5.0 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-59973](https://nvd.nist.gov/vuln/detail/CVE-2026-59973)
- [https://github.com/agentfront/mcp-from-openapi/pull/7](https://github.com/agentfront/mcp-from-openapi/pull/7)
- [https://github.com/agentfront/mcp-from-openapi/releases/tag/v2.5.0](https://github.com/agentfront/mcp-from-openapi/releases/tag/v2.5.0)
- [https://github.com/agentfront/frontmcp/commit/96a78eaa5c6c4bc51cced557d83d1a03344cb03d](https://github.com/agentfront/frontmcp/commit/96a78eaa5c6c4bc51cced557d83d1a03344cb03d)
- [https://github.com/agentfront/frontmcp/pull/496](https://github.com/agentfront/frontmcp/pull/496)
- [https://github.com/agentfront/frontmcp/releases/tag/v1.5.0](https://github.com/agentfront/frontmcp/releases/tag/v1.5.0)
- [https://github.com/agentfront/frontmcp/security/advisories/GHSA-65h7-9wrw-629c](https://github.com/agentfront/frontmcp/security/advisories/GHSA-65h7-9wrw-629c)
- [https://github.com/agentfront/mcp-from-openapi/commit/be3409cce6e97642696d4ee5a4e4e2712490b277](https://github.com/agentfront/mcp-from-openapi/commit/be3409cce6e97642696d4ee5a4e4e2712490b277)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)