CVE-2026-53712
TLS MITM can downgrade SCRAM-SHA-256-PLUS to SCRAM-SHA-256 in com.ongres.scram <3.3
Is CVE-2026-53712 being exploited?
Not confirmed. CVE-2026-53712 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-53712?
CVE-2026-53712 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53712?
Yes. A fix has been recorded for CVE-2026-53712. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53712 affect?
CVE-2026-53712 affects com.ongres.scram:scram-client (<3.3), com.ongres.scram:scram-common (<3.3), Java apps using SCRAM-SHA-256-PLUS with channel binding. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53712?
Upgrade to com.ongres.scram version 3.3+ and validate TLS cert handling
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
TLS man-in-the-middle can remove channel binding, downgrading authentication and enabling credential interception or session impersonation.
Patch when possible
- affected< 3.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.