CVE-2026-53712

HighCVSS 8.2

Published: 17/07/2026(UTC)Updated: 24/10/2026(UTC)Translated: 25/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.26%

18th percentile - higher than 18% of all known CVEs

Summary

A vulnerability in the SCRAM library allows an attacker performing a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS with channel binding to standard SCRAM-SHA-256 without channel binding. The issue occurs when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519, and getChannelBindingData() can return an empty byte array after NoSuchAlgorithmException.

Risk Assessment

An attacker can intercept and modify traffic, downgrading authentication security, potentially leading to credential theft or user impersonation.

Recommendation

Update the scram-client and scram-common libraries to version 3.3 or later.

Other vulnerabilities in SCRAM

CVE-2025-59432Medium
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the SASL authentication mechanisms. Prior to version 3.2, the Java implementation of SCRAM contains a timing attack vulnerability because Arrays.equals was used to compare values such as client proofs and server signatures, performing a short-circuit comparison. Differences in execution time could allow an attacker to infer sensitive authentication material.

Original NVD description (English source)

SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to 3.3, a flaw in com.ongres.scram:scram-client and com.ongres.scram:scram-common allows an attacker capable of a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS with channel binding to standard SCRAM-SHA-256 without channel binding when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519; getChannelBindingData() can return an empty byte array after NoSuchAlgorithmException, and the ScramClient builder treats that as absent channel-binding data. This issue is fixed in version 3.3.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS