sec: document RUSTSEC-2026-0049 exception in deny.toml#257
Merged
Conversation
rustls-webpki 0.102.8 is pulled in transitively by rumqttc 0.25.1 via its use-rustls-no-provider feature. The patch (0.103.10) is semver- incompatible with rumqttc's ^0.102 requirement; no 0.102.x backport exists and upstream has not updated the constraint. The vulnerable copy only surfaces as the WebPki error type, not in the TLS handshake (which uses 0.103.10 via tokio-rustls). Dependabot alert #4 dismissed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ignoreentry forRUSTSEC-2026-0049indeny.tomltolerable_riskreasonWhy there is no code fix
rustls-webpki 0.102.8is pulled in transitively byrumqttc 0.25.1via itsuse-rustls-no-providerfeature (activated by ourtransport-mqtt-tlsfeature flag).0.102.xbackport0.103.10; the0.102series received no fixrumqttcrequiresrustls-webpki ^0.102;0.103.10doesn't satisfy thisrumqttc 0.25.1(crates.io) and itsmainbranch still require^0.102The vulnerable
0.102.8copy is used only as theWebPkierror type inrumqttc's TLS error enum. The actual TLS handshake and certificate verification userustls-webpki 0.103.10viatokio-rustls 0.26. Exploiting this requires compromising a trusted CA (CVSS 4.4).Unblock
Remove the
deny.tomlexception oncerumqttcpublishes a release that bumpsrustls-webpkito^0.103.🤖 Generated with Claude Code