CVE-2026-53712

SCRAM: Silent channel-binding authentication downgrade via unsupported certificate algorithms

Published Jul 17, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in the ongress scram-client and scram-common libraries allows an attacker capable of a TLS Man‑In‑The‑Middle (MITM) attack to silently downgrade a channel‑binding enabled SCRAM‑SHA‑256‑PLUS connection to a plain SCRAM‑SHA‑256 connection without channel binding by causing the client to interpret the absence of channel binding data as missing binding data during certificate processing.

Affected Systems

The affected software is com.ongres.scram:scram-client and com.ongres.scram:scram-common used by ongress scram implementations. All versions prior to 3.3 are vulnerable.

Risk and Exploitability

The CVSS v3 score is 8.2, indicating high severity while the EPSS score of less than 1% suggests a low likelihood of exploitation. The vulnerability is not listed in CISA KEV. An attacker would need a TLS MITM setup that can supply a modern signature algorithm such as Ed25519 in an X.509 certificate, which triggers the client to treat channel binding data as absent, effectively lowering authentication security.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to scram version 3.3 or later
  • Ensure server certificates use signature algorithms that the client supports and avoid unsupported algorithms such as Ed25519
  • If an immediate upgrade is not possible, enforce strict TLS verification to prevent MITM and consider rejecting connections that do not provide channel binding data

Generated by OpenCVE AI on July 30, 2026 at 23:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-p9jg-fcr6-3mhf OnGres SCRAM silent channel-binding authentication downgrade via unsupported certificate algorithms
History
Type Values Removed Values Added
First Time appeared Ongres
Ongres scram
Vendors & Products Ongres
Ongres scram
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title SCRAM: Silent channel-binding authentication downgrade via unsupported certificate algorithms
Weaknesses CWE-636
CWE-757
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N'}

Weaknesses
  • CWE-636

    Not Failing Securely ('Failing Open')

  • CWE-757

    Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 7:09 PM
Reserved
Jun 10, 2026, 4:43 PM
Status
Awaiting Analysis
Published
Jul 17, 2026, 7:17 PM
Modified
Oct 24, 2026, 8:10 PM