Summary
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
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | kimi-code | 0.42.0-bp160.1.1 |
Vulnerabilities 2
-
High 7.5
ws: Memory exhaustion DoS from tiny fragments and data chunks
ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer c…
-
Medium 4.4
ws: Uninitialized memory disclosure
ws is an open source WebSocket client and server for Node.js. Prior to 8.20.1, the websocket.close() implementation is vulnerable to uninitialized memory disclosure when a TypedArray is passed as the reason argument. This vulnerability is fixed in 8.20.1.