Security update for kimi-code
Published Sources: OSV
What is affected, what to do
The available sources name no fixed version. Check the vendor guidance in the references below.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 25.53 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
This update for kimi-code fixes the following issues:
Changes in kimi-code:
Update to version 0.42.0:
- Add an experimental Updates panel with paginated progress messages from the main agent and subagents, enabled with KIMI_CODE_EXPERIMENTAL_NOTIFY_USER=1
- Turn the subagent model pool, Remote Control and the minidb session-index read model with the global search worker always on; their experimental flags and opt-out variables are gone, search persistence is now tuned via the [database] section
- Give tower worker and reviewer briefings the full mission context, follow the subagent timeout for tower agents, and show each background agent's model in /tasks
- Retrieve file search matches beyond the first 100 results, accept HEIC, HEIF and BMP images with Kimi-served models, and warn in kimi -p when project MCP servers are skipped in an untrusted folder
- Read files with configurable character limits and resumable long-line reads, decode malformed UTF-16 with a warning, and preserve image and video filenames in session history
- Rework the dashboard: deletable sessions, reorderable media rail, collapsed tool calls revealed with Ctrl-O, and less jank on long conversations and session reloads
Update to version 0.41.0:
- Add experimental tower mode for multi-agent orchestration and Remote Control for reaching a local web session remotely
- Add the WaitFor tool so the agent can wait for a background task inside the current turn, and an optional fork parameter that starts a subagent from a snapshot of the caller's history
- Support two OAuth login methods, kimi.ai and kimi.com, and activate several skills in one prompt
- Enable the subagent model pool in every launch mode by default and make turn-level file history unconditional
- Add a dangerous-command guard that always asks before shutdown, reboot or rm -rf in manual and YOLO permission modes, disabled with [permission] dangerous_command_guard; auto mode never blocks
- Remove kimi web --allow-remote-terminals; PTY terminal routes are served on loopback binds only
- Require Edit and Write to read a file first, and reject a write when the file changed on disk since that read
- Rework the bundled web dashboard: multi-tab right sidebar, Open/Done/Workspaces session tabs, a plugin marketplace panel and mobile bottom sheets
- ... see upstream's release notes for the full list
- Vendor the runtime dependencies upstream stopped inlining in
0.39.0:
- Add ws, qrcode and qrcode's own pngjs and dijkstrajs as sources, installed into the package's private node_modules
- Unpack the npm tarball directly instead of running npm install, which would resolve the new dependencies against the registry and pull in qrcode's CLI-only yargs tree
- Declare the vendored trees with Provides: bundled(...)
- CVE-2026-48779: ws denial of service from a high volume of tiny WebSocket fragments; the ws inlined in the old bundle predated the 8.21.0 fix, the vendored ws is 8.21.3 (boo#1268927)
- CVE-2026-45736: ws uninitialized memory disclosure via websocket.close() with a TypedArray, fixed by the same ws version (boo#1269951)
- Load the compiled node-pty addon during the build check as well