KIMI-CODE · CVE-2026-126757 · AI agents & MCP
NO FIX YET
Kimi Code's Web UI honored a kimi_origin URL parameter on HTTP(S) pages. Per Moonshot's own PR #3964, a crafted link could redirect API requests, bearer token included, to an attacker-controlled origin. NVD frames it as an open redirect in isOriginAllowed, versions up to 2.5.2. The fix is described as landing in a separate repo (kimi-code-app#775) with the dist-web bundle synced later. No release note confirms it shipped, and 2.5.3 (2026-11-10) does not mention it.
first public Nov 11, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run the Kimi Code Web UI (versions up to 2.5.2) and click links to it from untrusted sources. A crafted link can send the UI's API requests, with the bearer token, to another origin, according to the maintainers' PR. CLI-only users who never start the Web UI can skip it. I could not confirm whether the current Web UI starts by default.
Not affected if cli-only-use
Who cares ai-coding-agent, kimi-code, web-ui
No fix yet, per the sources.
A security vulnerability has been detected in Moonshot AI Kimi Code up to 2.5.2. This affects the function isOriginAllowed of the file apps/kimi-code/dist-web/assets/index-HU0LCM-X.js of the component Web UI. Such manipulation of the argument kimi_origin leads to open redirect. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
This page as .md ·
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.