cve.bz

CVE-2026-126758 Moonshot AI Kimi Code WorkspaceDirsService local.toml reliance on untrusted inputs in a security decision

1.9 lowEPSS 0.1%

Low (1.9) in moonshot ai kimi code. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability was detected in Moonshot AI Kimi Code up to 2.0.2. This vulnerability affects unknown code of the file .kimi-code/local.toml of the component WorkspaceDirsService. Performing a manipulation of the argument additional_dir results in reliance on untrusted inputs in a security decision. The attack requires a local approach. The exploit is now public and may be used. Upgrading to version 2.1.0 is able to resolve this issue. Upgrading the affected component is recommended.

Severity

CVSS 4.0

1.9 low
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

4.4 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-807 Reliance on Untrusted Inputs in a Security Decision
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
Assigned by
VulDB (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126758 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126758?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126758?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126758 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126758

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126758](https://cve.bz/cve/badge/CVE-2026-126758.svg)](https://cve.bz/cve/CVE-2026-126758)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126758"><img src="https://cve.bz/cve/badge/CVE-2026-126758.svg" alt="CVE-2026-126758"></a>

Affected

  • moonshot ai:kimi code

Versions

From the CNA's record in the CVE List.

ProductAffected
Moonshot AI Kimi Code2.0.0
Moonshot AI Kimi Code2.0.1
Moonshot AI Kimi Code2.0.2

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

History

  1. Score 4.8 → 1.9 low
  2. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON