Skip to content

deps: bump h2 / rustls / wasmtime / webbrowser past open RustSec advisories - #521

Merged
send merged 1 commit into
mainfrom
send/fix-Vulnerabilities-FAILURE
Sep 26, 2026
Merged

send merged 1 commit into
mainfrom
send/fix-Vulnerabilities-FAILURE

Conversation

@send

@send send commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Summary

Licenses & Vulnerabilities (cargo deny) is failing on main and every PR (e.g. run 35838703540). Five advisories were the cause, and every one is fixed in a semver-compatible patch release:

Advisory Crate Before → After What it's about
RUSTSEC-2026-0258 h2 0.4.14 → 0.4.19 unbounded empty DATA frames
RUSTSEC-2026-0285 rustls 0.23.40 → 0.23.45 TLS 1.3 handshake messages accepted across encryption-level boundaries
RUSTSEC-2026-0268 wasmtime 47.0.3 → 47.0.4 guest-controlled-size host heap allocation through WASIp3 streams
RUSTSEC-2026-0269 wasmtime 47.0.3 → 47.0.4 filesystem sandbox escape via trailing slashes
RUSTSEC-2026-0257 webbrowser 1.2.1 → 1.2.4 Unix BROWSER argument injection
  • The rustls bump also brings in aws-lc-rs 1.17.0 → 1.18.1, aws-lc-sys 0.41.0 → 0.45.0 and rustls-webpki 0.103.13 → 0.103.15. A plain cargo update -p rustls stopped at 0.23.43, so I used --precise 0.23.45.
  • The wasmtime bump carries its cranelift / pulley / wasmtime-internal-* siblings with it (0.134.3→0.134.4 / 47.0.3→47.0.4).
  • In the workspace Cargo.toml, the version floors for the two direct dependencies now match the patched versions: wasmtime = "47.0.4" and rustls = "0.23.45". This follows the existing convention of a patch-level floor on wasmtime. I also updated the wasmtime floor's explanatory comment for the new advisories.

Verification (local)

  • cargo deny check with cargo-deny 0.20.2 (the same version CI uses): advisories ok, bans ok, licenses ok, sources ok.
    • The locally installed 0.19.0 cannot parse the advisory DB because of a duplicate ID (RUSTSEC-2026-0244), so I did not use it.
  • mise run check / lint / test-all (12785 passed) / doc / trip-wires: all EXIT=0.
  • After raising the floors in Cargo.toml: cargo check --workspace --all-features --locked passes and cargo fmt --check is clean.

🤖 Generated with Claude Code

…sories

The `Licenses & Vulnerabilities` (cargo deny) job fails on main and every PR
with five advisories, all fixed in semver-compatible patch releases:

- RUSTSEC-2026-0258 h2 0.4.14 -> 0.4.19 (unbounded empty DATA frames)
- RUSTSEC-2026-0285 rustls 0.23.40 -> 0.23.45 (TLS 1.3 handshake messages
  accepted across encryption-level boundaries); pulls aws-lc-rs 1.18.1 /
  aws-lc-sys 0.45.0 / rustls-webpki 0.103.15
- RUSTSEC-2026-0268 / RUSTSEC-2026-0269 wasmtime 47.0.3 -> 47.0.4 (WASIp3
  stream host allocation; filesystem sandbox escape via trailing slashes)
- RUSTSEC-2026-0257 webbrowser 1.2.1 -> 1.2.4 (BROWSER argument injection)

The workspace floors for the two direct deps are raised to the patched
versions (wasmtime "47.0.4", rustls "0.23.45"), following the existing
load-bearing patch-floor convention on wasmtime.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-26T05:34:05.199127Z e7fc788 PR opened
ℹ️ 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.

@send
send merged commit a75f566 into main Sep 26, 2026
7 checks passed
@send
send deleted the send/fix-Vulnerabilities-FAILURE branch September 26, 2026 05:49
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