CVE-2026-53712
| Severity | 8.2 High CVSS 4.0 |
|---|---|
| Fixed in | 3.3 |
| Weakness | CWE-636 |
| Published | 17 Jul 2026 |
| Updated | 24 Oct 2026 |
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.
CWE-757
Exploitation status
No public exploit
No exploit has been reported in the sources we check.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment exploitation: none
- Indexed PoC none indexed
- EPSS 0.26% chance in 30 days
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all |
|---|---|
| Finding | This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious. |
| Candidate fix | https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf : the maintainers' own security advisory: names the version that fixes it, so the fix is the difference between two releases |
Affected software and releases
Maven packages
Affected and fixed versions, from OSV.dev| Package | Introduced | Fixed | Last affected |
|---|---|---|---|
com.ongres.scram:scram-client |
0 | 3.3 |
unbounded |
com.ongres.scram:scram-common |
0 | 3.3 |
unbounded |
Products and versions
2 products, 2 version entries| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| osv | com.ongres.scram | scram-client | generic | < 3.3 |
| osv | com.ongres.scram | scram-common | generic | < 3.3 |
References
| URL | Tags |
|---|---|
| https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf | advisory |
| https://github.com/ongres/scram | PACKAGE |
| https://github.com/ongres/scram/releases/tag/3.3 |
Timeline
Timeline
| Published | 2026-07-17 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-10-24 | NVD's own last-modified date for this record. |