# CVE-2026-17534: Kimi Code FetchURL SSRF protection bypass via DNS-resolving hostnames and redirects

> Attackers can bypass SSRF protections in Kimi Code to access internal network services via DNS rebinding or redirects, potentially exposing sensitive data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-28vq-345c-25gg

## What is CVE-2026-17534?

CVE-2026-17534 is a medium-severity server-side request forgery vulnerability in MoonshotAI Kimi Code, published on 27 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

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

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


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

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

## Is CVE-2026-17534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17534 is a medium-severity server-side request forgery vulnerability in MoonshotAI Kimi Code, published on 27 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-17534 in the wild and no public exploit code.

Affected product: MoonshotAI Kimi Code. 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-17534/ (Markdown: https://insights.sbomify.com/CVE-2026-17534/index.md)
```

## Sources

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

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