Is there a public PoC exploit available for CVE-2026-19765?

Yes, a public proof-of-concept exploit is available for CVE-2026-19765. Prioritise patching immediately. EPSS: 0.2%.

swagger-testcase-mcp CVE-2026-19765

Q: What is the CVSS score of CVE-2026-19765?

CVE-2026-19765 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-58559 LOW

Server-Side Request Forgery (SSRF) (CWE-918)

2026-08-14 VulDB

GHSA-4324-vhrx-x39p

SSRF Swagger Testcase Mcp

2.1

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

2.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.3 MEDIUM

Network-exploitable SSRF requiring low-privilege authentication (PR:L); limited C/I/A impact, no scope change absent confirmed metadata chaining.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 14, 2026 - 01:28 vuln.today

Severity Changed

Aug 14, 2026 - 01:22 NVD

MEDIUM LOW

CVSS changed

Aug 14, 2026 - 01:22 NVD

5.3 (MEDIUM) 2.1 (LOW)

CVE Published

Aug 14, 2026 - 01:00 cve.org

LOW 2.1

DescriptionCVE.org

A security flaw has been discovered in eyaushev swagger-testcase-mcp 5babb27c951fb404bc2b25ec80593616e49054e5. This vulnerability affects the function loadSource of the file src/utils/swagger-parser.ts of the component fetch_swagger. Performing a manipulation results in server-side request forgery. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

AnalysisAI

Server-side request forgery in eyaushev swagger-testcase-mcp enables authenticated remote attackers to forge arbitrary server-side HTTP requests through the loadSource function of the fetch_swagger component, potentially reaching internal network resources, cloud metadata endpoints, or other services inaccessible from the attacker's position. All versions under the project's rolling release model are affected at commit 5babb27c951fb404bc2b25ec80593616e49054e5, with no patch or maintainer response confirmed at time of analysis. A public proof-of-concept exploit exists via GitHub issue, though no active exploitation has been confirmed by CISA KEV; the CVSS 4.0 base score of 2.1 reflects limited but real impact across confidentiality, integrity, and availability on the vulnerable system.

Technical ContextAI

swagger-testcase-mcp is a Model Context Protocol (MCP) server tool by eyaushev designed to generate test cases from Swagger/OpenAPI specifications. The vulnerability exists in the loadSource function within src/utils/swagger-parser.ts, which belongs to the fetch_swagger component responsible for retrieving external Swagger definitions. CWE-918 (Server-Side Request Forgery) indicates that user-controlled URL input is passed to a server-side HTTP fetch operation without adequate URL validation, allowlisting, or network-layer restrictions. This allows an attacker to substitute arbitrary target URLs, causing the server process to issue outbound requests on their behalf. The affected CPE is cpe:2.3:a:eyaushev:swagger-testcase-mcp:*:*:*:*:*:*:*:*, covering the entire product line with no version floor, consistent with the rolling release strategy noted in the disclosure.

RemediationAI

No vendor-released patch has been identified at time of analysis; the project maintainer has not responded to the coordinated disclosure reported via GitHub issue #1 (https://github.com/eyaushev/swagger-testcase-mcp/issues/1). As a primary compensating control, enforce egress network filtering on the host running swagger-testcase-mcp to block outbound requests to RFC 1918 private address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and link-local addresses (169.254.0.0/16), which prevents the most common SSRF pivot targets including cloud metadata endpoints - note this may restrict legitimate Swagger fetches from internal hosts and should be tuned accordingly. As a secondary control, implement application-layer URL allowlisting in loadSource to restrict accepted Swagger source URLs to a known-safe list of external domains, rejecting any IP-literal URLs or non-HTTPS schemes; this requires a local code patch. Access to the MCP server should be restricted to trusted users only, limiting who can invoke fetch_swagger. Monitor https://vuldb.com/cve/CVE-2026-19765 and the GitHub repository for patch availability.