# CVE-2026-53712: SCRAM: Silent channel-binding authentication downgrade via unsupported certificate algorithms

> An attacker can bypass SCRAM channel binding security features via TLS man-in-the-middle attacks when modern certificate algorithms are used.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-p9jg-fcr6-3mhf

## What is CVE-2026-53712?

CVE-2026-53712 is a high-severity vulnerability in ongres scram, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-757 (Selection of Less-Secure Algorithm During Negotiation), CWE-636 (Not Failing Securely)

## Which versions are affected by CVE-2026-53712?

4 open source packages ship an affected version, including com.ongres.scram:scram-client and com.ongres.scram:scram-common.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ongres.scram:scram-client` | Maven | All versions | 3.3 |
| `com.ongres.scram:scram-client` | Maven | All versions | 3.3 |
| `com.ongres.scram:scram-common` | Maven | All versions | 3.3 |
| `com.ongres.scram:scram-common` | Maven | All versions | 3.3 |

## How do I fix CVE-2026-53712?

Upgrade com.ongres.scram:scram-client to 3.3 or later.

## Is CVE-2026-53712 being exploited?

There is no known exploitation of CVE-2026-53712 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53712 and fix it if it is affected.

What it is: CVE-2026-53712 is a high-severity vulnerability in ongres scram, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53712 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.ongres.scram:scram-client (Maven): affected all versions; fixed in 3.3
- com.ongres.scram:scram-client (Maven): affected all versions; fixed in 3.3
- com.ongres.scram:scram-common (Maven): affected all versions; fixed in 3.3
- com.ongres.scram:scram-common (Maven): affected all versions; fixed in 3.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53712/ (Markdown: https://insights.sbomify.com/CVE-2026-53712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53712
- OSV: https://osv.dev/vulnerability/CVE-2026-53712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53712/
Summaries are generated and may contain mistakes; the official description above is the record.