Moonshot AI Kimi Code authorization bypass in Plan Mode permission guard
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
Moonshot AI Kimi Code has an improper authorization flaw in its Plan Mode Permission Guard, in the guardToolExecution function. A local attacker with low-privilege access can trigger it without any user interaction.
Written by a model
Original description
A weakness has been identified in Moonshot AI Kimi Code up to 2.7.2. This vulnerability affects the function guardToolExecution of the file packages/agent-core-v2/src/features/plan/planService.ts of the component Plan Mode Permission Guard. Executing a manipulation can lead to improper authorization. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134006 (Moonshot AI Kimi Code Plan Mode Permission Guard planService.ts guardToolExecution improper authorization), 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-134006 (entry last updated 2026-11-21):
Affected:
- Moonshot AI Kimi Code: versions 2.7.0, 2.7.1, 2.7.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-134006 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134006 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/441599
- https://vuldb.com/vuln/441599/cti
- https://vuldb.com/cve/CVE-2026-134006
- https://vuldb.com/submit/1052054
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-134006
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-134006"}.Affected versions
- Moonshot AI Kimi Code2.7.0, 2.7.1, 2.7.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch5/5No patch listed yet
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134006 |
| Record | NVD · CVE-2026-134006 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | mcniyfj5bw9b.feishu.cn · docx/B9lIdyhBAovYrkxl4JPchVyinWf |
| Other links 4 | |
| Advisory | VulDB · Advisory #441599 |
| Advisory | VulDB · Threat intelligence #441599 |
| Advisory | VulDB · CVE-2026-134006 record |
| Advisory | VulDB · Submission #1052054 |
Questions about CVE-2026-134006
Is CVE-2026-134006 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: cve.now feed data
Which versions are affected by CVE-2026-134006?
Kimi Code: versions 2.7.0, 2.7.1, 2.7.2.
Source: cve.now feed data
Related
- CVE-2026-126757Moonshot AI Kimi Code Web UI index-HU0LCM-X.js isOriginAllowed redirect
- CVE-2026-95660Moonshot AI Kimi Code MCP Configuration Loader config-loader.ts os command injection
- CVE-2026-126758Moonshot AI Kimi Code WorkspaceDirsService local.toml reliance on untrusted inputs in a security decision
- CVE-2026-129056WordPress Authorizer plugin < 3.17.2 - Privilege Escalation vulnerability
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
No corrections so far. Something wrong on this page? Report an error.