LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25046: [Kimi VS Code] Command Injection in publish scripts vsix-publish.js and ovsx-publish.js

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.

LowCVSS 2.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-25046 is a low-severity command injection issue in MoonshotAI kimi-agent-sdk development publish scripts. It affects repository maintainers or developers running those scripts, not users of the published VS Code extension. A maliciously named VSIX file could cause unintended commands to run during publishing.

Executive priority

Treat as low priority unless your organization builds or publishes from this repository. The main risk is compromise of developer or release environments, not customer systems. Patch during normal maintenance or before the next publishing activity.

Technical view

Before kimi-agent-sdk 0.1.6, vsix-publish.js and ovsx-publish.js passed filenames into execSync() as shell command strings. Filenames containing shell metacharacters could trigger command injection. The fix replaces execSync with execFileSync using array arguments. The vulnerable files are repository development scripts and are not included in the published VS Code extension.

Likely exposure

Exposure is limited to developers or release automation using the affected repository scripts before version 0.1.6. End users of the published VS Code extension are not affected, according to the advisory.

Exploitation context

The reported scenario requires local access or influence over VSIX filenames, high privileges, and user interaction to run the publish scripts. The source bundle indicates this is not in CISA KEV, and no cited source reports active exploitation.

Researcher notes

This is CWE-77 command injection with CVSS 2.9. Scope is narrow: development scripts only, pre-0.1.6, requiring a crafted filename and script execution. Avoid treating the VS Code extension as affected unless new evidence contradicts the advisory.

Mitigation direction

  • Upgrade kimi-agent-sdk to version 0.1.6 or later.
  • If upgrade is delayed, ensure VSIX filenames are safe before running publish scripts.
  • Restrict who can add or rename VSIX files in release directories.
  • Review release automation that runs repository publish scripts.

Validation and detection

  • Confirm the repository or package version is 0.1.6 or later.
  • Check whether vsix-publish.js or ovsx-publish.js are used in workflows.
  • Verify publish scripts no longer call execSync with shell command strings.
  • Confirm release directories do not contain unsafe VSIX filenames.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25046 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.9CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N0.32.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.9Low
CVSS 3.1 vector shape for CVE-2026-25046Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MoonshotAIkimi-agent-sdk< 0.1.6Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.