High, CVSS 8.3PyPIAmendedPublished
gmaps-mcp's unauthenticated HTTP transport allows unlimited Google Maps API calls at operator expense
GHSA-52cq-7v8r-62c6
- Affected
- PyPI gmaps-mcp <= 0.1.2
- Fixed in
- 0.1.3· Vendor fix available
- Issue
- Unauthenticated HTTP Transport Allows Unlimited Google Maps API Calls at Operator Expense The gmaps-mcp codebase was reviewed at commit e671db68c804c9e67d51582d3280839ffa65f127 and three issues worth flagging were discovered — one high-severity, one medium, one structural. There were no preexisiting CVEs for this package yet and the repository had no prior security issues. The primary issue is that the HTTP transport in server.py skips authentication entirely when MCPAPIKEY is not set — which is the default, since .env.example ships the key as a blank value. Any unauthenticated caller who knows the server's public URL can invoke all six tools and generate live, billed Google Maps API requests against the operator's key. Because the README explicitly instructs operators to expose the server via ngrok (ngrok http 8000, then point MCP clients at the ngrok URL), this configuration gets deployed internet-facing as a matter of normal usage. Affected files and exact lines:…
Recommended action: Upgrade to 0.1.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.