# CVE-2026-105222: alexpechkarev/google-maps through 12.16 Disabled TLS Certificate Verification via ssl_verify_peer

> On-path attackers can intercept Google Maps API requests and steal keys because the library disables TLS certificate verification by default.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-mpgp-p4pg-fp7c

## What is CVE-2026-105222?

CVE-2026-105222 is a critical vulnerability in alexpechkarev google-maps, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The alexpechkarev/google-maps Laravel package through 12.16 disables TLS certificate verification by default because the bundled config sets ssl_verify_peer to FALSE, which is passed to CURLOPT_SSL_VERIFYPEER. On-path attackers can present any certificate to intercept Google Maps web-service requests, steal the API key from the query string, and tamper with responses.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-105222?


## How do I fix CVE-2026-105222?

No fix has been published for CVE-2026-105222 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105222 being exploited?

There is no known exploitation of CVE-2026-105222 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105222 and fix it if it is affected.

What it is: CVE-2026-105222 is a critical vulnerability in alexpechkarev google-maps, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105222 in the wild and no public exploit code.

Affected product: alexpechkarev google-maps. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105222/ (Markdown: https://insights.sbomify.com/CVE-2026-105222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105222
- OSV: https://osv.dev/vulnerability/CVE-2026-105222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105222/
Summaries are generated and may contain mistakes; the official description above is the record.