[5.1] Bump scram-client from 3.2 to 3.3 fixing CVE-2026-53712#1683
Closed
julianladisch wants to merge 1 commit into
Closed
[5.1] Bump scram-client from 3.2 to 3.3 fixing CVE-2026-53712#1683julianladisch wants to merge 1 commit into
julianladisch wants to merge 1 commit into
Conversation
scram-client 3.3 fixes a flaw that allows an attacker capable of performing a TLS machine-in-the-middle (MITM) attack to silently downgrade a connection from SCRAM-SHA-256-PLUS (with channel binding) to standard SCRAM-SHA-256 (without channel binding), bypassing strict client-side enforcement policies. See GHSA-p9jg-fcr6-3mhf and https://github.com/ongres/scram/releases/tag/3.3
Contributor
Author
|
5.1 is not affected because is uses the default "prefer"/"allow" channel binding policy and not the affected "strict" channel binding policy: |
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.
scram-client 3.3 fixes a flaw that allows an attacker capable of performing a TLS machine-in-the-middle (MITM) attack to silently downgrade a connection from SCRAM-SHA-256-PLUS (with channel binding)
to standard SCRAM-SHA-256 (without channel binding), bypassing strict client-side enforcement policies.
See GHSA-p9jg-fcr6-3mhf and https://github.com/ongres/scram/releases/tag/3.3