Description

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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-14T01:18:57.637Z",
  "pubdate": "2026-08-14T01:18:57.637Z",
  "executiveSummary": "A Server-Side Request Forgery (SSRF) vulnerability has been identified in eyaushev swagger-testcase-mcp commit 5babb27c951fb404bc2b25ec80593616e49054e5. This security flaw resides within the loadSource function inside the src/utils/swagger-parser.ts file of the fetch_swagger component. The vulnerability allows remote attackers to induce the affected application into issuing arbitrary outbound HTTP requests, potentially leading to internal network reconnaissance, unauthorized data access, or interaction with internal microservices that are otherwise inaccessible from the external perimeter. The product utilizes a rolling release model, meaning specific affected version tags are not formally delineated. Public exploits are currently available, increasing the risk of active exploitation. The project maintainers have been notified via an issue report but have not yet provided a response or official patch.",
  "technicalDetails": "The vulnerability is caused by improper input validation and handling of user-supplied URIs or input strings within the loadSource function located in src/utils/swagger-parser.ts. When the fetch_swagger component processes input to retrieve Swagger or OpenAPI specifications, it fails to adequately sanitize or restrict the destination URLs parsed by the underlying HTTP request mechanism.\nAttackers can exploit this flaw remotely by supplying a malicious payload containing arbitrary internal or external URLs (such as loopback addresses, internal metadata endpoints like 169.254.169.254, or internal network services) to the vulnerable parameter. When the application executes the loadSource function, it initiates an outbound connection to the attacker-specified destination on behalf of the server.\nThe attack vector is network-based, allowing unauthenticated remote actors to trigger requests depending on the exposure of the application interface. Network exposure and remote accessibility of the component dictate the feasibility of the attack. Post-exploitation impact includes the potential retrieval of sensitive internal configuration data, scanning of internal network topologies, and bypassing perimeter access controls by leveraging the trust boundary of the hosting server."
}