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.
CVE-2026-53712
HIGHPre-NVD 8.28.2—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EPSS
- 17.6%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026Patch available. Sources: github_release, github.
github Patch Available
Silent channel-binding authentication downgrade via unsupported certificate algorithms · Advisory · ongres/scram · GitHub
https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhfgithub_release Patch Available
SCRAM Java 3.3
Patch available: ongres/scram 3.3
https://github.com/ongres/scram/releases/tag/3.3Vendor Advisories for CVE-2026-53712(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Maven(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| com.ongres.scram:scram-client | 3.0, 3.1, 3.2 | 3.3 | — |
| com.ongres.scram:scram-common | 3.0, 3.1, 3.2 | 3.3 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:51 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 18:35 UTCEG score recompute▲ 8.20
- 2026-07-17 18:34 UTCMITRE cvelistV5CVSS v3 → 8.2 · CVSS v4 → 8.2
- 2026-07-01 22:02 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-53712?
CVE-2026-53712 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-53712 disclosed?
CVE-2026-53712 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53712 actively exploited?
CVE-2026-53712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53712?
CVE-2026-53712 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-53712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53712, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53712
Is Your Infrastructure Affected by CVE-2026-53712?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.