PT-2026-55221 · Maven+2 · Com.Ongres.Scram:Scram-Client+2
CVE-2026-53712
·
Published
2026-07-01
·
Updated
2026-07-17
CVSS v4.0
8.2
High
| Vector | AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N |
Name of the Vulnerable Software and Affected Versions
com.ongres.scram:scram-client versions prior to 3.3
com.ongres.scram:scram-common versions prior to 3.3
Description
A flaw in
com.ongres.scram:scram-client and com.ongres.scram:scram-common allows an attacker performing a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS (which uses channel binding) to standard SCRAM-SHA-256 (without channel binding). This occurs when TlsServerEndpoint processes an X.509 certificate using modern signature algorithms, such as Ed25519. In these cases, the getChannelBindingData() function can return an empty byte array after a NoSuchAlgorithmException occurs, which the ScramClient builder then interprets as absent channel-binding data rather than a failure. This bypasses strict client-side enforcement policies in deployments where channel binding is required.Recommendations
Update com.ongres.scram:scram-client to version 3.3 or later.
Update com.ongres.scram:scram-common to version 3.3 or later.
Stop using the
getChannelBindingData() function in TlsServerEndpoint and transition to getChannelBindingHash() to ensure NoSuchAlgorithmException is correctly propagated.
Use the ChannelBindingPolicy API during client construction to explicitly enforce security boundaries.Exploit
Fix
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Com.Ongres.Scram:Scram-Client
Com.Ongres.Scram:Scram-Common
Scram