CVE-2026-17534

published 27 Jul 2026 · updated 27 Jul 2026

Kimi Code FetchURL SSRF protection bypass via DNS-resolving hostnames and redirects

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.27.0.

Kimi Code (@moonshot-ai/kimi-code) before 0.27.0 implements FetchURL SSRF hardening as a static hostname and IP-literal denylist in assertSafeFetchTarget, without resolving DNS or re-validating hosts after HTTP redirects. An attacker who can influence a FetchURL call (for example via prompt injection) can supply a crafted public hostname that resolves to loopback or another internal address, or a public URL that redirects to such a target, and thereby reach internal network services that the denylist was intended to block. FetchURL is included in the default auto-approve tool set, so the call does not require interactive user confirmation in manual mode.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MoonshotAI<0.27.00.27.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-17534 severity on Zeptric[![CVE-2026-17534](https://zeptric.io/badge/cve/CVE-2026-17534.svg)](https://zeptric.io/cve/CVE-2026-17534)