Skip to main content
CVE-2026-17534VulnerabilityPublished

CVE-2026-17534: MoonshotAI Kimi Code · Server-Side Request Forgery (SSRF)

Affects MoonshotAI Kimi CodeSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.27.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.27.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Kimi Code and @moonshot-ai/kimi-code to 0.27.0.

Affected software

ProductAffectedFixed in
MoonshotAIKimi CodeAffected
  • <0.27.0
Fixed in
  • 0.27.0
GitHub@moonshot-ai/kimi-codepkg:github/@moonshot-ai/kimi-codeOther threatsAffected
  • <0.27.0
Fixed in
  • 0.27.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should avoid using vulnerable versions of Kimi Code or disable the FetchURL function if possible. Additional mitigations include restricting network access from the application to internal services and monitoring for unusual FetchURL usage.

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.

References

Community reviews

Loading reviews…