CVE-2026-126757

Moonshot AI Kimi Code Web UI index-HU0LCM-X.js isOriginAllowed redirect

  • Medium 5.3
  • A public exploit reference is listed

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.

Key facts

Published
11 Nov 2026
Last changed
11 Nov 2026
Assigned by
VulDB
EPSS
0.336% likely to be exploited in the next 30 days, higher than 27.392% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 4.0, Mediumfrom the CNA (VulDB)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
  • 4.3CVSS 3.1, Mediumfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:X/RC:C
  • 4.3CVSS 3.0, Mediumfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:X/RC:C
  • 5.0CVSS 2.0, Mediumfrom the CNA (VulDB)AV:N/AC:L/Au:N/C:N/I:P/A:N/E:POC/RL:ND/RC:C

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Moonshot AIKimi Code
  • 2.5.0 (affected)
  • 2.5.1 (affected)
  • 2.5.2 (affected)

Timeline

  1. 11 Nov 2026 Advisory disclosed
  2. 11 Nov 2026 VulDB entry created
  3. 11 Nov 2026 VulDB entry last update
  4. 11 Nov 2026 Published

Weakness

References