CVE-2026-53712

HIGHPre-NVD 8.28.2—
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 83% 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
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
Patch 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-3mhf
github_release Patch Available

SCRAM Java 3.3

Patch available: ongres/scram 3.3

https://github.com/ongres/scram/releases/tag/3.3

Vendor Advisories for CVE-2026-53712(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatscram-common2026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
com.ongres.scram:scram-client3.0, 3.1, 3.23.3—
com.ongres.scram:scram-common3.0, 3.1, 3.23.3—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 70× 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.

  1. 2026-08-25 16:15 UTCEG score recompute
  2. 2026-08-25 16:15 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 23:06 UTCEG score recompute
  5. 2026-08-24 23:06 UTCVendor advisory
  6. 2026-08-24 10:41 UTCEG score recompute
  7. 2026-08-24 10:41 UTCVendor advisory
  8. 2026-08-23 20:49 UTCVendor advisory
  9. 2026-08-23 08:24 UTCVendor advisory
  10. 2026-08-22 19:53 UTCVendor advisory
  11. 2026-08-22 06:54 UTCEG score recompute
  12. 2026-08-22 06:54 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 17:50 UTCVendor advisory
  15. 2026-08-21 05:25 UTCEG score recompute
  16. 2026-08-21 05:25 UTCVendor advisory
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 17:00 UTCVendor advisory
  19. 2026-08-20 04:35 UTCEG score recompute
  20. 2026-08-20 04:35 UTCVendor advisory
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-19 09:53 UTCVendor advisory
  23. 2026-08-18 20:57 UTCVendor advisory
  24. 2026-08-18 04:47 UTCVendor advisory
  25. 2026-08-17 13:50 UTCEG score recompute
Show 61 more
  1. 2026-08-17 13:50 UTCVendor advisory
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 01:26 UTCEG score recompute
  4. 2026-08-17 01:26 UTCVendor advisory
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 13:01 UTCEG score recompute
  7. 2026-08-16 13:01 UTCVendor advisory
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-16 00:36 UTCVendor advisory
  10. 2026-08-15 12:11 UTCEG score recompute
  11. 2026-08-15 12:11 UTCVendor advisory
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 23:46 UTCVendor advisory
  14. 2026-08-14 11:21 UTCVendor advisory
  15. 2026-08-12 22:06 UTCEG score recompute
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 21:17 UTCEG score recompute
  18. 2026-08-11 08:53 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 19:38 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 18:49 UTCEG score recompute
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 17:59 UTCEG score recompute
  25. 2026-08-06 17:09 UTCEG score recompute
  26. 2026-08-06 13:47 UTCEPSS rescore
  27. 2026-08-06 04:44 UTCEG score recompute
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-05 03:23 UTCEG score recompute
  30. 2026-08-04 15:10 UTCEPSS rescore
  31. 2026-08-04 14:41 UTCEG score recompute
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-03 13:51 UTCEG score recompute
  34. 2026-08-03 10:36 UTCEPSS rescore
  35. 2026-08-02 12:59 UTCEG score recompute
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 12:09 UTCEG score recompute
  38. 2026-08-01 04:16 UTCEPSS rescore
  39. 2026-07-30 22:51 UTCEG score recompute
  40. 2026-07-30 16:28 UTCEPSS rescore
  41. 2026-07-30 10:26 UTCEG score recompute
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-28 19:37 UTCEG score recompute
  44. 2026-07-28 15:37 UTCEPSS rescore
  45. 2026-07-27 18:32 UTCEG score recompute
  46. 2026-07-26 17:38 UTCEG score recompute
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 05:10 UTCEG score recompute
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-24 14:18 UTCEPSS rescore
  51. 2026-07-23 14:18 UTCEPSS rescore
  52. 2026-07-23 03:19 UTCEG score recompute
  53. 2026-07-22 14:08 UTCEPSS rescore
  54. 2026-07-20 17:08 UTCEPSS rescore
  55. 2026-07-19 14:31 UTCEPSS rescore
  56. 2026-07-19 14:31 UTCEPSS rescore
  57. 2026-07-19 03:51 UTCEG score recompute
  58. 2026-07-19 02:29 UTCEPSS rescore
  59. 2026-07-17 18:35 UTCEG score recompute▲ 8.20
  60. 2026-07-17 18:34 UTCMITRE cvelistV5CVSS v3 → 8.2 · CVSS v4 → 8.2
  61. 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 23, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 82.7% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-53712?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs