Skip to content

AAK-MCP-GOOGLESEARCH-CVE-2026-19337-001: adenot mcp-google-search SSRF via the read_webpage url argument (0.3.1 or earlier, no fix released)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
AdenotMcpGoogleSearchReadWebpageSsrf

What it detects

@adenot/mcp-google-search up to and including 0.3.1 has server-side request forgery in its read_webpage tool (src/index.ts): the url argument is fetched without validating the host or scheme, so an indirect prompt injection can steer the server to fetch attacker-chosen internal endpoints (cloud metadata, loopback admin ports, RFC-1918 hosts) and return the response (CVE-2026-19337, CVSS 5.3). The affected artifact is the scoped npm package @adenot/mcp-google-search (versions 0.1.0–0.3.1, latest 0.3.1); the unscoped mcp-google-search (latest 1.0.0) is an unrelated package and is not pinned. No patched release is published yet — the upstream fix (commit f071d491) is unreleased — so every published version is treated as exposed (presence-only pin). Same SSRF-via-tool-argument shape as the astrbot MCP-test-endpoint pin.

How to fix

Remove or replace the @adenot/mcp-google-search read_webpage server until a fixed release ships. If it must run, put it behind an egress allow-list that blocks loopback / link-local / metadata / RFC-1918 targets, and validate the url scheme and host before fetching. Re-pin to the fixed version once upstream publishes a patched release.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-GOOGLESEARCH-CVE-2026-19337-001

Limitations

Reads @adenot/mcp-google-search in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, and reports every version, a future fixed one included, until the pin gets a floor. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json), in .cursor/mcp.json or .vscode/mcp.json, or in a lockfile format the reader does not parse (a Yarn 2+ yarn.lock). A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-GOOGLESEARCH-CVE-2026-19337-001.md: the page then shows that text, with the registry reference appended under it.