Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

gmaps-mcp's unauthenticated HTTP transport allows unlimited Google Maps API calls at operator expense

GHSA-52cq-7v8r-62c6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gmaps-mcp 0.1.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-52cq-7v8r-62c6

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-52cq-7v8r-62c6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-52cq-7v8r-62c6

Advisory: gmaps-mcp's unauthenticated HTTP transport allows unlimited Google Maps API calls at operator expense
IDs: GHSA-52cq-7v8r-62c6
Record: https://patchnext.com/advisories/ghsa-52cq-7v8r-62c6 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gmaps-mcp 0.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gmaps-mcp: affected <= 0.1.2; fixed in 0.1.3

## Suggested inspection (read-only)
- `python -m pip show gmaps-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gmaps-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-52cq-7v8r-62c6 (OSV record GHSA-52cq-7v8r-62c6 lists affected ranges: PyPI gmaps-mcp >=0 <0.1.3 (fixed))
- Verified: https://github.com/advisories/GHSA-52cq-7v8r-62c6 (GitHub-reviewed advisory GHSA-52cq-7v8r-62c6 lists affected ranges: PyPI gmaps-mcp >=0 <=0.1.2)

Commands are suggestions: review each one before running it.

Loading voting…