chore(deps): bump quinn-proto from 0.11.13 to 0.11.14

[dependabot]

Bumps quinn-proto from 0.11.13 to 0.11.14.

Release notes

Sourced from quinn-proto's releases.

quinn-proto 0.11.14

@​jxs reported a denial of service issue in quinn-proto 5 days ago:

• GHSA-6xvm-j4wr-6v98

We coordinated with them to release this version to patch the issue. Unfortunately the maintainers missed these issues during code review and we did not have enough fuzzing coverage -- we regret the oversight and have added an additional fuzzing target.

Organizations that want to participate in coordinated disclosure can contact us privately to discuss terms.

What's Changed

• Fix over-permissive proto dependency edge by @​Ralith in quinn-rs/quinn#2385
• 0.11.x: avoid unwrapping VarInt decoding during parameter parsing by @​djc in quinn-rs/quinn#2559

Commits

• 2c315aa proto: bump version to 0.11.14
• 8ad47f4 Use newer rustls-pki-types PEM parser API
• c81c028 ci: fix workflow syntax
• 0050172 ci: pin wasm-bindgen-cli version
• 8a6f82c Take semver-compatible dependency updates
• e52db4a Apply suggestions from clippy 1.91
• 6df7275 chore: Fix unnecessary_unwrap clippy
• c8eefa0 proto: avoid unwrapping varint decoding during parameters parsing
• 9723a97 fuzz: add fuzzing target for parsing transport parameters
• eaf0ef3 Fix over-permissive proto dependency edge (#2385)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[MattMagg]

@codex review this PR thoroughly

[MattMagg]

@claude review this PR thoroughly

[claude]

Claude finished @MattMagg's task in 1m 46s —— View job

---

PR Review: chore(deps): bump quinn-proto from 0.11.13 to 0.11.14

Todo List

• Gather context and understand the PR
• Review the security advisory (GHSA-6xvm-j4wr-6v98)
• Inspect Cargo.lock changes
• Check quinn-proto usage in the codebase
• Assess build/compatibility impact
• Provide final review summary

---

Security Advisory: GHSA-6xvm-j4wr-6v98

This is a security patch addressing a Denial-of-Service (DoS) vulnerability in the QUIC protocol implementation. The root cause was an unchecked .unwrap() on VarInt decoding during QUIC transport parameter parsing. A malicious peer could craft a handshake packet with malformed transport parameters that would trigger a panic, crashing the process.

Fix: quinn-rs/quinn#2559 — replaced .unwrap() with proper error handling that returns an error instead of panicking, preventing process termination.

Severity: Medium (remote DoS against services accepting inbound QUIC connections). The fix is minimal, targeted, and low-risk.

---

Cargo.lock Diff Analysis

The diff is clean and exactly what is expected for this version bump. There are 4 distinct changes:

1. quinn-proto version + checksum update ✅

- version = "0.11.13"
- checksum = "f1906b49b0c3bc04b5fe5d86a77925ae6524a19b816ae38ce1e426255f1d8a31"
+ version = "0.11.14"
+ checksum = "434b42fec591c96ef50e21e886936e66d3cc3f737104fdb9b737c40ffb94c098"

The new checksum is the legitimate published crate. This is the primary intended change.

2–4. windows-sys bump: 0.52.0 → 0.60.2 ✅

Three packages update their windows-sys dependency as a transitive consequence of quinn-proto 0.11.14's "Fix over-permissive proto dependency edge" change (quinn-rs/quinn#2385):

• mio (event loop library)
• quinn-udp (UDP socket abstraction)
• rustix (low-level syscall abstraction)

This is an expected and legitimate side effect. All three packages have semver-compatible support for windows-sys 0.60.x. The workspace still retains multiple windows-sys versions (0.48.0, 0.52.0, 0.60.2, 0.61.2) where other crates need them — this is normal for Cargo dependency resolution.

---

Dependency Chain in Mister Smith

quinn-proto is a transitive dependency — it is not directly declared in any workspace Cargo.toml. The path is:

mister-smith-llm (anthropic/openai/claude-subscription features)
└── reqwest 0.12.28
    └── quinn 0.11.9
        └── quinn-proto 0.11.14  ← patched

mister-smith-mcp
└── rmcp 1.1.1 (transport-streamable-http-client-reqwest feature)
    └── reqwest → quinn → quinn-proto  ← same path

The workspace declares reqwest with features = ["json", "stream", "rustls-tls"] — HTTP/3 is not explicitly enabled. However, quinn appears in the lock file because rmcp's transport-streamable-http-client-reqwest feature brings in reqwest with additional transports. Regardless, the lock file confirms quinn-proto is compiled as part of this workspace and the patch applies.

---

Verdict: ✅ APPROVE — Merge Immediately

Check	Result
Only Cargo.lock modified	✅ Correct — no source changes needed for a lock-only bump
Checksums match published crate	✅ Verified
No unexpected dependency additions	✅ Clean
windows-sys bump is legitimate	✅ Expected transitive consequence
Addresses a real CVE/advisory	✅ GHSA-6xvm-j4wr-6v98 (DoS fix)
Breaking change risk	✅ None — patch release, lock-only change
Dependabot compatibility score	✅ Shown as compatible

This is a straightforward, low-risk security patch. The only file changed is Cargo.lock, the change is exactly scoped to the version bump, and the vulnerability being fixed (remote DoS via crafted QUIC handshake) justifies prompt merging. No action needed beyond approving.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".