Skip to main content
CVE-2026-25046VulnerabilityPublished Updated

CVE-2026-25046: MoonshotAI kimi-agent-sdk · Command Injection

Affects MoonshotAI kimi-agent-sdkSource CVE Database V5

0

Not known to be exploited · CVSS 2.9 Low : upgrade to 0.1.6 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.6
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade kimi-agent-sdk and moonshotai/kimi-agent-sdk to 0.1.6.

Affected software

ProductAffectedFixed in
MoonshotAIkimi-agent-sdkAffected
  • <0.1.6
Fixed in
  • 0.1.6
GitHubmoonshotai/kimi-agent-sdkpkg:github/moonshotai/kimi-agent-sdkOther threatsAffected
  • <0.1.6
Fixed in
  • 0.1.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should upgrade the kimi-agent-sdk to version 0.1.6 or later, where the vulnerability is fixed by using execFileSync() with argument arrays to safely handle filenames. Until upgrading, developers must ensure that all .vsix files or other inputs used by the vsix-publish.js and ovsx-publish.js scripts have sanitized filenames free of shell metacharacters such as $(), ``, ;, &, |, or other command injection vectors. Implement strict filename validation or whitelisting in build and publish scripts. Restrict access to development environments and scripts to trusted personnel only. Employ code review and static analysis tools to detect unsafe use of execSync() or similar functions in scripts. Additionally, consider running development scripts in isolated containers or sandboxes to limit the impact of potential command injection. Regularly audit development tools and scripts for security best practices to prevent similar issues.

Description

Kimi Agent SDK is a set of libraries that expose the Kimi Code (Kimi CLI) agent runtime in applications. The vsix-publish.js and ovsx-publish.js scripts pass filenames to execSync() as shell command strings. Prior to version 0.1.6, filenames containing shell metacharacters like $(cmd) could execute arbitrary commands. Note: This vulnerability exists only in the repository's development scripts. The published VSCode extension does not include these files and end users are not affected. This is fixed in version 0.1.6 by replacing execSync with execFileSync using array arguments. As a workaround, ensure .vsix files in the project directory have safe filenames before running publish scripts.

References

Community reviews

Loading reviews…