Vulnerabilities in pkg:maven/com.ongres.scram/scram-common
PACKAGECVE-2026-53712 is a HIGH ongres scram silent channel-binding authentication vulnerability (CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')) affecting Scram client libraries in the Maven ecosystem. The issue involves ongres scram silent channel-binding authentication downgrade via unsupported certificate algorithms. Remediation is available by upgrading affected packages to version 3.3.
pkg:maven/com.ongres.scram/scram-common
Vulnerability advisories affecting package pkg:maven/com.ongres.scram/scram-common. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-p9jg-fcr6-3mhf | CVE-2026-53712 | HIGH | OnGres SCRAM silent channel-binding authentication downgrade via unsupported certificate algorithms |
| GHSA-3wfh-36rx-9537 | CVE-2025-59432 | MODERATE | Timing Attack Vulnerability in SCRAM Authentication |
CVE-2026-53712 at a Glance
How to Fix CVE-2026-53712
To remediate this vulnerability, upgrade all affected Scram client dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>com.ongres.scram</groupId>
<artifactId>scram-client</artifactId>
<version>3.3</version>
</dependency>
<dependency>
<groupId>com.ongres.scram</groupId>
<artifactId>scram-common</artifactId>
<version>3.3</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=com.ongres.scram
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-53712, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=com.ongres.scram
Analyze the terminal output to locate any version of Scram client in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3), your application is affected.
Note: The mvn dependency:tree -Dincludes=com.ongres.scram command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade'), where a protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties. In Scram client, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-53712 Affected Scram client Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
com.ongres.scram:scram-client
|
Maven |
< 3.3
|
3.3
|
|
com.ongres.scram:scram-common
|
Maven |
< 3.3
|
3.3
|
References
Frequently Asked Questions
What is CVE-2026-53712?
Which Scram client versions are affected?
What version fixes CVE-2026-53712?
Is scram-client affected?
Is scram-common affected?
What CWE is associated with CVE-2026-53712?
How can I check Maven dependencies for CVE-2026-53712?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-p9jg-fcr6-3mhf",
"modified" : "2026-07-01T21:51:17Z",
"published" : "2026-07-01T21:51:17Z",
"aliases" : [ "CVE-2026-53712" ],
"summary" : "OnGres SCRAM silent channel-binding authentication downgrade via unsupported certificate algorithms",
"details" : "## Summary\n\nA flaw in `com.ongres.scram:scram-client` allows an attacker capable of performing a TLS man-in-the-middle (MITM) attack to silently downgrade a connection from `SCRAM-SHA-256-PLUS` (with channel binding) to standard `SCRAM-SHA-256` (without channel binding), bypassing strict client-side enforcement policies.\n\n## Component Breakdown\n\nThis occurs due to a two-part failure in `TlsServerEndpoint` when a server presents an `X.509` certificate using a modern signature algorithm that lacks traditional `WITH` naming structures (such as `Ed25519` or post-quantum algorithms):\n\n1. The internal hash derivation method fails to parse the algorithm name, swallows the resulting `NoSuchAlgorithmException, and silently returns an empty byte array via the deprecated `getChannelBindingData()` API.\n2. The client builder mistakenly interprets this empty byte array as an environmental absence of channel binding data rather than a cryptographic failure, falling back to non-channel-bound authentication.\n\n## Impact & Scope\n\nThis issue only impacts deployments where the downstream application layer explicitly enforces strict channel binding enforcement (e.g., channelBinding=require in pgJDBC).\n\nDrivers operating under a \"prefer\" or \"allow\" policy (used by default) are structurally insulated from an unhandled exception since a fallback to standard SCRAM is within their expected configuration.\n\n## Remediation\n\nUpdate your project configuration to pull in version 3.3 or later of the SCRAM library, which introduces strict exception propagation and explicit policy controls.\n\nIf you are interacting with the `ScramClient` builder API directly (e.g., writing a custom driver or database extension):\n\n- Migrate Deprecated APIs: Stop using `TlsServerEndpoint.getChannelBindingData()`. Transition immediately to `TlsServerEndpoint.getChannelBindingHash()`, which correctly propagates `NoSuchAlgorithmException` up the stack.\n- Adopt Explicit Policies: Leverage the newly introduced `ChannelBindingPolicy` API during client construction. Do not rely on implicit parameter presence to dictate your security boundaries.\n\n```java\nScramClient client = ScramClient.builder()\n .advertisedMechanisms(serverMechanisms)\n .username(user)\n .password(pass)\n // Explicitly enforce strict boundaries if needed.\n .channelBindingPolicy(ChannelBindingPolicy.REQUIRE) \n .channelBinding(TlsServerEndpoint.TLS_SERVER_END_POINT, certHash)\n .build();\n```",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "com.ongres.scram:scram-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.3"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.2"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "com.ongres.scram:scram-common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.3"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.2"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/ongres/scram"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-636", "CWE-757" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-01T21:51:17Z",
"nvd_published_at" : null
}
}