Skip to content

fix(deps): resolve RUSTSEC-2026-0457/0461/0462 (rmcp 3.5.0 → 3.9.0) - #469

Closed
hyperpolymath wants to merge 1 commit into
mainfrom
claude/zen-brahmagupta-opqqle-w0-deps
Closed

hyperpolymath wants to merge 1 commit into
mainfrom
claude/zen-brahmagupta-opqqle-w0-deps

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Dependency audit and the rust-ci cargo audit are red on main, so every PR fails them. The cause is three advisories against rmcp 3.5.0, which crates/echidna-mcp depends on as version = "3":

Advisory Issue Fixed in
RUSTSEC-2026-0457 The OAuth client's SSRF filter checks host strings, not resolved addresses 3.7.0
RUSTSEC-2026-0461 Unbounded tool-schema cache in the Streamable HTTP server transport 3.6.0
RUSTSEC-2026-0462 Unbounded response-body buffering in Streamable HTTP clients 3.9.0

This is the same shape as #457 and #460.

Changes

  • Cargo.lock only. The command was cargo update -p rmcp -p rmcp-macros --precise 3.9.0 on the pinned toolchain (1.99.0).
    • rmcp and rmcp-macros go from 3.5.0 to 3.9.0. rmcp 3.9.0 newly lists libc and sha2 0.11, both already in the lock.
    • The lock also re-points some Windows-only windows-sys and getrandom edges (anstyle-query, colored, errno, rustix, socket2 and others). The pinned cargo makes the identical change on a no-op cargo update -p rmcp --precise 3.5.0, so it is the resolver's output on the current index, not part of the upgrade. No other package changes version.

RSR Quality Checklist

Required

  • Tests pass: see Testing. echidna-mcp has no tests of its own.
  • Code is formatted: no source change.
  • Linter is clean: cargo clippy --locked -p echidna-mcp -- -D warnings is clean.
  • No banned language patterns
  • SPDX headers: no new files.
  • No secrets

As Applicable

  • New dependencies reviewed for licence compatibility: none new. libc and sha2 are already in the tree, and rmcp keeps its licence at a minor release.

Testing

Check Result
cargo audit -f Cargo.lock on main's lock 3 vulnerabilities, which reproduces CI
cargo audit -f Cargo.lock on this branch 0 vulnerabilities, exit 0
cargo test --locked -p echidna-mcp builds; the crate has 0 tests
cargo clippy --locked -p echidna-mcp -- -D warnings clean

Not verified: runtime behaviour of the MCP server on 3.9.0. The crate has no tests, so this shows only that the API still compiles.


Generated by Claude Code

The "Dependency audit" and the rust-ci audit fail on main for three
advisories against rmcp 3.5.0, which echidna-mcp depends on as
`version = "3"`:
- RUSTSEC-2026-0457: the OAuth client's SSRF filter checks host
  strings, not resolved addresses;
- RUSTSEC-2026-0461: unbounded tool-schema cache in the Streamable
  HTTP server transport;
- RUSTSEC-2026-0462: unbounded response-body buffering in Streamable
  HTTP clients.

`cargo update -p rmcp -p rmcp-macros --precise 3.9.0` on the pinned
toolchain (1.99.0). rmcp 3.9.0 adds libc and sha2 0.11 to its own
dependency list.

The lockfile also re-points some Windows-only `windows-sys` and
`getrandom` edges (anstyle-query, colored, errno, rustix, socket2 and
others). The pinned cargo makes that same change on a no-op
`cargo update -p rmcp --precise 3.5.0`, so it is the resolver's output
on the current index, not part of this upgrade. No package versions
other than rmcp and rmcp-macros change.

cargo audit -f Cargo.lock: 0 vulnerabilities (was 3).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WS4mfQeC3N1DWjcCQJaQqw
@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 1

  • Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: a353c1d0-7630-49e2-9b7d-c49fc40c9ea7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@linear-code
linear-code Bot marked this pull request as ready for review November 9, 2026 13:02
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T13:03:44.283609Z 74b39ec Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sonarqubecloud

sonarqubecloud Bot commented Nov 9, 2026

Copy link
Copy Markdown

Copy link
Copy Markdown
Owner Author

Closing as a duplicate of #465. That PR carries the same rmcp 3.5.0 → 3.9.0 lock change (the Cargo.lock diff between the two branches is empty). It also fixes main's other two red checks: rustfmt in proof_search.rs and the Hypatia Zig-cast findings.


Generated by Claude Code

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.

3 participants