# CVE-2026-19337: adenot mcp-google-search read_webpage index.ts server-side request forgery

> An attacker with local execution access can exploit a server-side request forgery vulnerability in the read_webpage function to access internal resources.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-jg2j-2qmx-58vq

## What is CVE-2026-19337?

CVE-2026-19337 is a medium-severity server-side request forgery vulnerability in adenot mcp-google-search, published on 9 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in adenot mcp-google-search up to 0.3.1. Impacted is an unknown function of the file src/index.ts of the component read_webpage. Executing a manipulation of the argument url can lead to server-side request forgery. The attack is restricted to local execution. This patch is called f071d491b685011ca04e8ab8d586fc65f86bcee1. It is advisable to implement a patch to correct this issue.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-19337 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19337 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19337 is a medium-severity server-side request forgery vulnerability in adenot mcp-google-search, published on 9 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19337 exists.

Affected product: adenot mcp-google-search. 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-19337/ (Markdown: https://insights.sbomify.com/CVE-2026-19337/index.md)
```

## Sources

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

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