A critical server-side request forgery vulnerability in ShadowCloneLabs GlutamateMCPServers allows unauthenticated attackers to perform unauthorized requests to internal network resources.

The vulnerability is a Server-Side Request Forgery (CWE-918) located in the src/puppeteer/index.ts file. Unauthenticated attackers can supply a malicious URL to the puppeteer_navigate function, which is then processed by the headless browser without validation, enabling access to internal services or cloud metadata.

Successful exploitation permits an attacker to bypass network perimeters and interact with services reachable from the server but not exposed to the public internet. This can lead to the exfiltration of sensitive cloud credentials, internal system information, or unauthorized interaction with internal APIs, resulting in significant data compromise and potential escalation of access. While the CVSS score is 7.3, the potential for internal network traversal warrants immediate attention.

Immediate Action: As no official patch is currently available, administrators should restrict network access to the MCP/HTTP interface to trusted IP ranges only. Furthermore, implement strict egress filtering on the server to prevent access to internal RFC1918 addresses and cloud metadata services.

Proactive Monitoring: Monitor server access logs for anomalous requests to the MCP/HTTP interface, specifically looking for unusual URL parameters passed to the puppeteer_navigate tool.

Compensating Controls: Deploy a Web Application Firewall (WAF) or an API gateway in front of the interface to inspect and block requests containing suspicious URL schemes or attempts to access internal loopback addresses.

Public Exploit Available: Yes, a published proof-of-concept exists and is documented in the security researcher's write-up at the referenced GitHub issue.

Given the lack of a vendor-supplied patch, users must treat this vulnerability with high urgency. Administrators should apply the recommended network-level mitigations immediately to prevent potential unauthorized access to internal resources. Monitoring for signs of exploitation is essential until a formal security update is released by the maintainers.