fix(deps): bump lettre to 0.11.22 (RUSTSEC-2026-0141)#772
Merged
Conversation
Resolves the critical advisory flagged by `cargo audit` in CI. Perry's lettre usage is on the rustls-tls path (`tokio1-rustls-tls`), so the underlying BoringSSL hostname-verification bug does not apply in practice — but the lockfile bump silences the audit failure and keeps us on the patched release.
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
lettrefrom 0.11.21 → 0.11.22 inCargo.lockto clear the new critical advisory RUSTSEC-2026-0141 ("TLS hostname verification disabled when using Boring TLS backend"), which is currently failing thesecurity-auditworkflow onmain.perry-ext-nodemailer,perry-stdlib'sbundled-nodemailerfeature) uses thetokio1-rustls-tlsfeature, not the BoringSSL backend, so the underlying bug is not exploitable in practice — but bumping to the patched release silencescargo auditand keeps us current.Cargo.tomlchange needed: the workspace requirement islettre = "0.11", which already allows 0.11.22.The other entries in the failing audit log (
bincodev1,number_prefix,paste,rustls-pemfilev2) areunmaintainedwarnings on transitive deps with no in-tree replacement; they don't fail the audit and are out of scope here.Test plan
cargo check -p perry-ext-nodemailer -p perry-stdlib --features perry-stdlib/bundled-nodemailersucceeds locallysecurity-auditjob goes greencargo-test/lint/parity/compile-smokestay green