CVE-2026-53712

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.

CVSS

No CVSS.

References

Link	Resource
https://github.com/ongres/scram/releases/tag/3.3
https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf

Configurations

No configuration.

History

24 Oct 2026, 20:10

Type	Values Removed	Values Added
Summary		(es) SCRAM (Mecanismo de Autenticación de Respuesta a Desafío Salado) es parte de la familia de mecanismos de autenticación de la Capa de Autenticación y Seguridad Simple (SASL, RFC 4422). Antes de la versión 3.3, una falla en com.ongres.scram:scram-client y com.ongres.scram:scram-common permite a un atacante capaz de un ataque man-in-the-middle de TLS degradar silenciosamente una conexión de SCRAM-SHA-256-PLUS con enlace de canal a SCRAM-SHA-256 estándar sin enlace de canal cuando TlsServerEndpoint procesa un certificado X.509 utilizando un algoritmo de firma moderno como Ed25519; getChannelBindingData() puede devolver un array de bytes vacío después de NoSuchAlgorithmException, y el constructor ScramClient trata eso como datos de enlace de canal ausentes. Este problema está solucionado en la versión 3.3.

Information

Published : 2026-07-17 19:17

Updated : 2026-10-24 20:10

NVD link : CVE-2026-53712

Mitre link : CVE-2026-53712

CVE.ORG link : CVE-2026-53712

JSON object : View

Products Affected

No product.

CWE

CWE-636

Not Failing Securely ('Failing Open')

CWE-757

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

{"id": "CVE-2026-53712", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-53712", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-17T19:08:59.374984Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.2, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "HIGH", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "ongres", "product": "scram", "versions": [{"status": "affected", "version": "< 3.3"}]}]}], "published": "2026-07-17T19:17:16.880", "references": [{"url": "https://github.com/ongres/scram/releases/tag/3.3", "source": "security-advisories@github.com"}, {"url": "https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-636"}, {"lang": "en", "value": "CWE-757"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "SCRAM (Mecanismo de Autenticaci\u00f3n de Respuesta a Desaf\u00edo Salado) es parte de la familia de mecanismos de autenticaci\u00f3n de la Capa de Autenticaci\u00f3n y Seguridad Simple (SASL, RFC 4422). Antes de la versi\u00f3n 3.3, una falla en com.ongres.scram:scram-client y com.ongres.scram:scram-common permite a un atacante capaz de un ataque man-in-the-middle de TLS degradar silenciosamente una conexi\u00f3n de SCRAM-SHA-256-PLUS con enlace de canal a SCRAM-SHA-256 est\u00e1ndar sin enlace de canal cuando TlsServerEndpoint procesa un certificado X.509 utilizando un algoritmo de firma moderno como Ed25519; getChannelBindingData() puede devolver un array de bytes vac\u00edo despu\u00e9s de NoSuchAlgorithmException, y el constructor ScramClient trata eso como datos de enlace de canal ausentes. Este problema est\u00e1 solucionado en la versi\u00f3n 3.3."}], "lastModified": "2026-10-24T20:10:00.137", "sourceIdentifier": "security-advisories@github.com"}