Skip to content

chore(deps): bump rusqlite 0.41 and rmcp 3.9 - #153

Closed
asto18089 wants to merge 2 commits into
pinvou3-cleanfrom
deps/sqlite-rmcp-cve
Closed

asto18089 wants to merge 2 commits into
pinvou3-cleanfrom
deps/sqlite-rmcp-cve

Conversation

@asto18089

@asto18089 asto18089 commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Lands the two RUSTSEC advisories the parent repo's cargo deny hard gate surfaced on 2026-11-10:

  • RUSTSEC-2026-0459 / CVE-2026-119375 — bundled SQLite < 3.54.0 (libsqlite3-sys 0.38.2 via rusqlite 0.40.2, bundled) can return uninitialized page-cache memory when a database is opened alongside a sibling -wal file whose page size differs. Local attack vector: a crafted file pair makes ordinary queries return stale process memory. rusqlite 0.40.2 → 0.41.1 pulls libsqlite3-sys 0.39.1 (SQLite 3.54.1).
  • RUSTSEC-2026-0462 — rmcp < 3.9.0 Streamable HTTP clients read non-streaming response bodies unbounded; a malicious or compromised MCP server could OOM the host during initialize, pre-authentication. rmcp 3.7.0 → 3.9.0 (16 MiB JSON / 64 KiB error-body caps, streaming byte counts).

Verification (local, Linux arm64): codewhale-tui dev build green on the bumped graph; cargo deny check advisories clears both entries; test subsets green — mcp 381/0, memory 47/0, session 56/0 (the forkguard engine tests hang on the base pin in this sandbox as well — pre-existing environment issue, exercised on CI). The parent-repo PR pins the submodule at this commit.

No-Issue: dependency-only security bumps forced by the parent repo cargo-deny hard gate (fresh RUSTSEC advisories 2026-0459/0462/0430); no CodeWhale behavior change intended.

asto18089 added a commit to Pinvou/pinvou-agent that referenced this pull request Nov 10, 2026
The cargo-deny hard gate surfaced two fresh advisories against the
src-tauri lock graph (both rides on the CodeWhale submodule, which
stops the links = sqlite3 unification from bumping in this repo alone):

- RUSTSEC-2026-0459 (CVE-2026-119375): bundled SQLite < 3.54.0 in
  libsqlite3-sys 0.38.2 returns uninitialized page-cache memory for a
  database + mismatched-page-size -wal pair (local, crafted files).
  rusqlite requirement 0.40.2 -> 0.41.0, lock lands 0.41.1 /
  libsqlite3-sys 0.39.1 (SQLite 3.54.1).
- RUSTSEC-2026-0462: rmcp < 3.9.0 Streamable HTTP clients buffer
  non-streaming bodies unbounded (pre-auth OOM against a malicious MCP
  server). Lock lands rmcp 3.9.0 via the submodule bump
  (Pinvou/CodeWhale#153, submodule now 843319d39 on pinvou3-clean).

Verified on the unified graph: clippy -D warnings green; lib suite
4087/0/18; cargo deny advisories ok (offline, cached advisory DB).
Knowledge lane carries the same rusqlite bump separately.

Signed-off-by: asto <asto18089@126.com>
probe added 2 commits November 10, 2026 17:36
rusqlite 0.40.2 -> 0.41.1 (workspace), pulling libsqlite3-sys
0.38.2 -> 0.39.1: RUSTSEC-2026-0459 / CVE-2026-119375 -- bundled SQLite
< 3.54.0 can return uninitialized page-cache memory when a database is
opened alongside a sibling -wal file whose page size differs (local
attack vector; a crafted file pair makes ordinary queries return stale
process memory). libsqlite3-sys 0.39.1 bundles SQLite 3.54.1.

rmcp 3.7.0 -> 3.9.0 (tui): RUSTSEC-2026-0462 -- the Streamable HTTP
clients read non-streaming response bodies unbounded before 3.9.0, so a
malicious or compromised MCP server could OOM the host during
initialize, pre-authentication (16 MiB JSON / 64 KiB error caps from
3.9.0).

Verified: dev build of codewhale-tui green; advisories clear both
entries; mcp (381), memory (47), session (56) subsets green; the
forkguard engine tests hang on the base pin in this sandbox as well
(pre-existing local-environment issue, exercised on CI runners).

Signed-off-by: probe <probe@l4>
Path traversal in the Kitty graphics protocol handler (substring guard
instead of a component check, no .. rejection): untrusted terminal
output can delete and read files outside the temp directory. 0.5.28 ->
0.5.29 rides teletypewriter to the same patch release; cargo deny
advisories now fully green on this graph.

Signed-off-by: probe <probe@l4>
@asto18089
asto18089 force-pushed the deps/sqlite-rmcp-cve branch from e67ff25 to ec1a454 Compare November 10, 2026 09:38
@asto18089

Copy link
Copy Markdown
Collaborator Author

Closing in favor of #152 which landed the same three bumps (rusqlite 0.41 / rmcp 3.9 / rio-vt 0.5.29) concurrently — no reason to keep a duplicate open. The parent-repo PR will pin the gitlink at the #152 merge commit.

@asto18089 asto18089 closed this Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant