CVE-2026-126758 json
Moonshot AI Kimi Code WorkspaceDirsService local.toml reliance on untrusted inputs in a security decision
published 11h ago modified 11h ago also EUVD-2026-124146
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Moonshot AI Kimi Code 2.1.0
Is CVE-2026-126758 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploits and checks
- mcniyfj5bw9b.feishu.cn https://mcniyfj5bw9b.feishu.cn/docx/LsJldjpjXomkb4xTJ6CcWzdFnvd referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | 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 |
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L/E:P/RL:O/RC:C |
| CNA | 3.0 | 4.4 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L/E:P/RL:O/RC:C |
| CNA | 2.0 | 3.2 | AV:L/AC:L/Au:S/C:N/I:P/A:P/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.9 | 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 2.0 | 3.2 | AV:L/AC:L/Au:S/C:N/I:P/A:P |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | kimi-code | moonshotai/kimi-code | 2.0.0 2.0.1 2.0.2 |
Affected products
- Moonshot AI Kimi Code
Classification
References
-
github.com
/MoonshotAI/kimi-code/releases/tag/%40moonshot-ai%2Fkimi-code%402.1.0
patch
-
mcniyfj5bw9b.feishu.cn
/docx/LsJldjpjXomkb4xTJ6CcWzdFnvd
exploit
-
vuldb.com
/vuln/435868
vdb-entry, technical-description
-
vuldb.com
/vuln/435868/cti
signature, permissions-required
-
vuldb.com
/cve/CVE-2026-126758
third-party-advisory
-
vuldb.com
/submit/1033260
third-party-advisory
Sources
- CVE List CVE-2026-126758
- NVD CVE-2026-126758
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.