Skip to content

fix(deps): update rustls for RUSTSEC-2026-0285 - #379

Merged
cxymds merged 1 commit into
mainfrom
cxymds/fix-rustls-advisory
Sep 16, 2026
Merged

cxymds merged 1 commit into
mainfrom
cxymds/fix-rustls-advisory

Conversation

@cxymds

@cxymds cxymds commented Sep 16, 2026

Copy link
Copy Markdown
Member

Problem

The cargo-deny advisories check now fails on main with a security vulnerability, which blocks CI and the v0.1.36 release build:

error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ Cargo.lock:279:1
       ├ ID: RUSTSEC-2026-0285
       ├ Solution: Upgrade to >=0.23.45 (try `cargo update -p rustls`)
       ├ rustls v0.23.41

RUSTSEC-2026-0285 (GHSA-2mjx-qc3c-rqvc) affects rustls 0.23.41: a peer could send handshake messages that should be encrypted in plaintext without rustls rejecting the connection. Every release and PR pipeline that runs cargo deny check advisories fails until the lockfile is updated.

The same run also reports warning[yanked]: detected yanked crate for spin 0.10.0 (pulled in through crc-fast -> aws-smithy-checksums -> aws-sdk-s3).

Root cause

The workspace pins rustls 0.23.41 and spin 0.10.0 in Cargo.lock. The advisory for rustls was published after the lockfile was last refreshed, and spin 0.10.0 has since been yanked from crates.io.

Solution

Targeted lockfile refresh only, no manifest or source changes:

  • cargo update -p rustls -> rustls 0.23.45, rustls-webpki 0.103.15, aws-lc-rs 1.18.1, aws-lc-sys 0.45.0
  • cargo update -p spin@0.10.0 -> spin 0.10.1

Validation

Run on cxymds/fix-rustls-advisory (commit b3d024e):

  • cargo fmt --all --check - pass
  • cargo clippy --workspace --all-targets --locked -- -D warnings - pass, zero warnings
  • cargo test --workspace --locked - pass, 66 test targets, 0 failures
  • cargo deny check advisories - re-verified by CI on this PR

@cxymds
cxymds merged commit 1de7393 into main Sep 16, 2026
16 of 17 checks passed
@cxymds
cxymds deleted the cxymds/fix-rustls-advisory branch September 16, 2026 05:55
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