Update Rustls for RUSTSEC-2026-0285 - #917
Merged
Merged
Conversation
This was referenced Sep 14, 2026
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
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.
RUSTSEC-2026-0285, published September 14, flags the Rustls versions already locked on master. Update Research, Agent, SDK, proxy, and OpenSecret to Rustls 0.23.45, which fixes TLS 1.3 handshake encryption-level validation. Upstream advisory.
The patch changes only five Cargo.lock files. Research and OpenSecret also receive the required AWS-LC and WebPKI updates; OpenSecret needs the new minimum pkg-config version. Existing SDK versions and registry/path sources, TLS features, application protocol code, migrations, and PCR approval files are unchanged. This fix can merge independently before Transport V2 PR #873 is rebased.
Validation completed locally:
All local gates are complete. All 36 applicable hosted checks passed on commit dcca40e, including all four security scans, platform builds, and SDK/backend integration. The two EIF/PCR approval checks were skipped by their normal workflow conditions.
Deploying the backend fix later requires the normal rebuilt EIF, reviewed/signed PCR approvals, and deployment process. This ordinary dependency PR does not alter approvals or perform a deployment. Client rebuilds can ship their dependency update independently.