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 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.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

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.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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%
EPSS PROB
0.3%
EPSS %ILE
16th
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.
githubMentions a patch (unverified)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
com.ongres.scram:scram-client3.0, 3.1, 3.2
  • every version up to 3.3: fixed in 3.3
—
com.ongres.scram:scram-common3.0, 3.1, 3.2
  • every version up to 3.3: fixed in 3.3
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 141 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 06:48 UTCEG score recompute
  18. 2026-09-23 06:48 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 06:28 UTCEG score recompute
  22. 2026-09-18 06:28 UTCVendor advisory
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-14 00:21 UTCEG score recompute
Show 75 more
  1. 2026-09-14 00:21 UTCVendor advisory
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-13 09:06 UTCEG score recompute
  4. 2026-09-13 09:06 UTCVendor advisory
  5. 2026-09-12 14:36 UTCEG score recompute
  6. 2026-09-12 14:36 UTCVendor advisory
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 14:26 UTCEG score recompute
  12. 2026-09-06 14:26 UTCVendor advisory
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 00:36 UTCEG score recompute
  15. 2026-09-06 00:36 UTCVendor advisory
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 04:40 UTCEPSS rescore
  20. 2026-08-31 00:00 UTCEG score recompute
  21. 2026-08-31 00:00 UTCVendor advisory
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 11:34 UTCEG score recompute
  24. 2026-08-30 11:34 UTCVendor advisory
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-28 21:41 UTCEPSS rescore
  27. 2026-08-27 22:24 UTCEG score recompute
  28. 2026-08-27 22:24 UTCVendor advisory
  29. 2026-08-27 14:25 UTCEPSS rescore
  30. 2026-08-26 14:46 UTCEPSS rescore
  31. 2026-08-25 16:15 UTCEG score recompute
  32. 2026-08-25 16:15 UTCVendor advisory
  33. 2026-08-25 13:49 UTCEPSS rescore
  34. 2026-08-24 23:06 UTCEG score recompute
  35. 2026-08-24 23:06 UTCVendor advisory
  36. 2026-08-24 10:41 UTCEG score recompute
  37. 2026-08-24 10:41 UTCVendor advisory
  38. 2026-08-23 20:49 UTCVendor advisory
  39. 2026-08-23 08:24 UTCVendor advisory
  40. 2026-08-22 19:53 UTCVendor advisory
  41. 2026-08-22 06:54 UTCEG score recompute
  42. 2026-08-22 06:54 UTCVendor advisory
  43. 2026-08-21 23:49 UTCEPSS rescore
  44. 2026-08-21 17:50 UTCVendor advisory
  45. 2026-08-21 05:25 UTCEG score recompute
  46. 2026-08-21 05:25 UTCVendor advisory
  47. 2026-08-20 22:55 UTCEPSS rescore
  48. 2026-08-20 17:00 UTCVendor advisory
  49. 2026-08-20 04:35 UTCEG score recompute
  50. 2026-08-20 04:35 UTCVendor advisory
  51. 2026-08-19 17:04 UTCEPSS rescore
  52. 2026-08-19 09:53 UTCVendor advisory
  53. 2026-08-18 20:57 UTCVendor advisory
  54. 2026-08-18 04:47 UTCVendor advisory
  55. 2026-08-17 13:50 UTCEG score recompute
  56. 2026-08-17 13:50 UTCVendor advisory
  57. 2026-08-17 13:47 UTCEPSS rescore
  58. 2026-08-17 01:26 UTCEG score recompute
  59. 2026-08-17 01:26 UTCVendor advisory
  60. 2026-08-16 14:56 UTCEPSS rescore
  61. 2026-08-16 13:01 UTCEG score recompute
  62. 2026-08-16 13:01 UTCVendor advisory
  63. 2026-08-16 02:14 UTCEPSS rescore
  64. 2026-08-16 00:36 UTCVendor advisory
  65. 2026-08-15 12:11 UTCEG score recompute
  66. 2026-08-15 12:11 UTCVendor advisory
  67. 2026-08-15 01:30 UTCEPSS rescore
  68. 2026-08-14 23:46 UTCVendor advisory
  69. 2026-08-14 11:21 UTCVendor advisory
  70. 2026-08-12 22:06 UTCEG score recompute
  71. 2026-08-12 13:51 UTCEPSS rescore
  72. 2026-08-11 21:17 UTCEG score recompute
  73. 2026-08-11 08:53 UTCEG score recompute
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-09 19:38 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Maven:com.ongres.scram:scram-common

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 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.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53712?
CVE-2026-53712 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53712?
A fix for CVE-2026-53712 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53712 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs