High, CVSS 8.2MavenPublished
OnGres SCRAM silent channel-binding authentication downgrade via unsupported certificate algorithms
CVE-2026-53712 · GHSA-p9jg-fcr6-3mhf
- Affected
- Maven com.ongres.scram:scram-client <= 3.2
- Fixed in
- 3.3· Vendor fix available
- Issue
- A flaw in com.ongres.scram:scram-client allows an attacker capable of performing a TLS man-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. Component Breakdown This occurs due to a two-part failure in TlsServerEndpoint when a server presents an X.509 certificate using a modern signature algorithm that lacks traditional WITH naming structures (such as Ed25519 or post-quantum algorithms): 1. The internal hash derivation method fails to parse the algorithm name, swallows the resulting NoSuchAlgorithmException, and silently returns an empty byte array via the deprecated getChannelBindingData() API. 2. The client builder mistakenly interprets this empty byte array as an environmental absence of channel binding data rather than a cryptographic failure, falling back to non-channel-bound authentication. Impact & Scope…
Recommended action: Upgrade to 3.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.