Vulnerabilities in pkg:maven/org.postgresql/postgresql
PACKAGECVE-2026-54291 is a HIGH silent channel-binding authentication downgrade vulnerability (CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')) affecting PostgreSQL JDBC Driver libraries in the Maven ecosystem. The issue involves silent channel-binding authentication downgrade via unsupported certificate algorithms. Remediation is available by upgrading affected packages to version 42.7.12.
pkg:maven/org.postgresql/postgresql
Vulnerability advisories affecting package pkg:maven/org.postgresql/postgresql. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-j92g-9f8w-j867 | CVE-2026-54291 | HIGH | PostgreSQL JDBC Driver: Silent channel-binding authentication downgrade via unsupported certificate algorithms |
| GHSA-98qh-xjc8-98pq | CVE-2026-42198 | HIGH | pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS |
| GHSA-562r-vg33-8x8h | CVE-2022-41946 | MODERATE | TemporaryFolder on unix-like systems does not limit access to created files |
| GHSA-r38f-c4h4-hqq2 | CVE-2022-31197 | HIGH | PostgreSQL JDBC Driver SQL Injection in ResultSet.refreshRow() with malicious column names |
| GHSA-hq9p-pm7w-8p54 | CVE-2025-49146 | HIGH | pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration |
| GHSA-xfg6-62px-cxc2 | - | CRITICAL | Duplicate Advisory: SQL injection in pgjdbc |
| GHSA-88cc-g835-76rp | CVE-2020-13692 | HIGH | Improper Restriction of XML External Entity Reference |
| GHSA-24rp-q3w6-vc56 | CVE-2024-1597 | CRITICAL | org.postgresql:postgresql vulnerable to SQL Injection via line comment generation |
| GHSA-673j-qm5f-xpv8 | - | MODERATE | pgjdbc Arbitrary File Write Vulnerability |
| GHSA-727h-hrw8-jg8q | CVE-2022-26520 | LOW | Path traversal in org.postgresql:postgresql |
| GHSA-h86w-m5rm-xr33 | CVE-2012-1618 | HIGH | Unescaped parameters in the PostgreSQL JDBC driver |
| GHSA-v7wg-cpwc-24m4 | CVE-2022-21724 | HIGH | pgjdbc Does Not Check Class Instantiation when providing Plugin Classes |
CVE-2026-54291 at a Glance
How to Fix CVE-2026-54291
To remediate this vulnerability, upgrade all affected PostgreSQL JDBC Driver 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>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>42.7.12</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.postgresql
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-54291, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.postgresql
Analyze the terminal output to locate any version of PostgreSQL JDBC Driver in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 42.7.12), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.postgresql 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 PostgreSQL JDBC Driver, 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-54291 Affected PostgreSQL JDBC Driver Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.postgresql:postgresql
|
Maven |
≥ 42.7.4
< 42.7.12
|
42.7.12
|
References
Frequently Asked Questions
What is CVE-2026-54291?
Which PostgreSQL JDBC Driver versions are affected?
What version fixes CVE-2026-54291?
Is postgresql affected?
What CWE is associated with CVE-2026-54291?
How can I check Maven dependencies for CVE-2026-54291?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j92g-9f8w-j867",
"modified" : "2026-07-21T17:47:39Z",
"published" : "2026-07-21T17:47:39Z",
"aliases" : [ "CVE-2026-54291" ],
"summary" : "PostgreSQL JDBC Driver: Silent channel-binding authentication downgrade via unsupported certificate algorithms",
"details" : "### Impact\n\n`channelBinding=require` connections can be silently downgraded from `SCRAM-SHA-256-PLUS` (with channel binding) to plain `SCRAM-SHA-256` (without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has no `tls-server-end-point` channel-binding hash. Examples are `Ed25519`, `Ed448`, and post-quantum algorithms.\n\nTwo issues combine in releases 42.7.4 through 42.7.11:\n\n1. The bundled `com.ongres.scram:scram-client` (3.1 or 3.2) returns an empty byte array instead of failing when it cannot derive the binding hash for such a certificate. This is the library issue tracked as [GHSA-p9jg-fcr6-3mhf](https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf).\n2. pgJDBC does not enforce `channelBinding=require` where it matters. `ScramAuthenticator` checks only that the server *advertised* a `-PLUS` mechanism; it neither rejects the empty binding nor checks that the *negotiated* mechanism uses channel binding. The connection therefore downgrades silently, and would do so even against a fixed `scram-client`, because the missing enforcement is in pgJDBC's own code.\n\nOnly connections that set `channelBinding=require` are affected. Under the default `prefer` policy, and under `allow` or `disable`, falling back to plain SCRAM is the documented behaviour. Releases before 42.7.4 are unaffected, because they do not support channel binding.\n\n### Patches\n\nFixed in pgJDBC 42.7.12. pgJDBC now enforces channel binding in its own code, independently of the `scram-client` version:\n\n- Under `channelBinding=require`, it fails the connection when no channel-binding data can be extracted from the server certificate, instead of passing an empty value to the SCRAM client. The error names the certificate signature algorithm.\n- After negotiation, it requires the selected mechanism to use channel binding (a `-PLUS` mechanism) whenever `channelBinding=require` is set, regardless of how negotiation resolved.\n\nUpgrade to 42.7.12 or later.\n\n### Workarounds\n\nNo pgJDBC setting restores channel-binding enforcement on an affected release; upgrading is the fix.\n\nIf you cannot upgrade immediately, verify the server certificate at the TLS layer so that a man-in-the-middle cannot present a substitute certificate. Set `sslmode=verify-full` with a truststore that contains only your server's CA. This defence is independent of channel binding and blocks the same attacker. Connections that rely on `channelBinding=require` in place of certificate verification have no equivalent workaround and should upgrade.\n\n### References\n\n- [GHSA-p9jg-fcr6-3mhf](https://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf) — the related `com.ongres.scram:scram-client` issue (root cause of the empty channel-binding value).\n- `scram-client` 3.3 release (library fix): https://github.com/ongres/scram/releases/tag/3.3\n- pgJDBC fix in 42.7.12: [commit](https://github.com/pgjdbc/pgjdbc/commit/77df98e4e66c12936ded3478a0954f6f580bad99)",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.postgresql:postgresql"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "42.7.4"
}, {
"fixed" : "42.7.12"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-j92g-9f8w-j867"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54291"
}, {
"type" : "WEB",
"url" : "https://github.com/pgjdbc/pgjdbc/commit/77df98e4e66c12936ded3478a0954f6f580bad99"
}, {
"type" : "WEB",
"url" : "https://github.com/ongres/scram/releases/tag/3.3"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/pgjdbc/pgjdbc"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-636", "CWE-757" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-21T17:47:39Z",
"nvd_published_at" : "2026-07-06T19:17:08Z"
}
}