CVE-2026-54291: PostgreSQL JDBC Driver Channel Binding Downgrade Vulnerability

Technical summary

The vulnerability affects the SCRAM authentication path in pgjdbc. When channelBinding=require is set, the driver should enforce SCRAM-SHA-256-PLUS with channel binding, which binds the authentication handshake to the TLS connection's cryptographic parameters. However, the bundled scram-client library returns an empty byte array instead of failing when a certificate signature algorithm lacks a tls-server-end-point channel-binding hash. The ScramAuthenticator in pgjdbc only validates that the server advertised a PLUS mechanism (SCRAM-SHA-256-PLUS) but does not reject the empty binding or verify that the negotiated mechanism actually uses channel binding. This allows silent downgrade to plain SCRAM-SHA-256, which lacks the connection-binding guarantee. An attacker with network-level access (TLS interception capability) can exploit this by crafting a malicious certificate to trigger the empty-binding condition.

Business impact

For organizations relying on pgjdbc with channelBinding=require to protect database connections against interception, this vulnerability undermines a critical security control. Affected deployments lose man-in-the-middle protection without user awareness—the downgrade is silent, so administrators and developers may not realize their security posture has degraded. In environments where PostgreSQL is accessed over untrusted networks or where certificate-based authentication is a primary defense layer, this creates material risk of credential compromise or query tampering. The silent nature of the failure makes detection and forensic analysis harder than an obvious authentication failure would be.

Affected systems

PostgreSQL JDBC Driver (pgjdbc) versions 42.7.4 through 42.7.11 are affected. Any application using pgjdbc in this version range with channelBinding=require configured in the connection string is vulnerable. Systems not explicitly setting this parameter are not affected, as the default behavior does not require channel binding. Verify your pgjdbc version in your application's dependency tree or class path.

Exploitability

Exploitation requires network-level access to intercept or manipulate TLS traffic between the client and PostgreSQL server (MITM position). The attacker must also craft a TLS certificate with a signature algorithm that lacks a tls-server-end-point channel-binding hash. This is not trivial but is feasible in scenarios where an attacker controls network routing, operates a malicious proxy, or compromises network infrastructure. The attack is passive from the driver's perspective—no user interaction is needed. CVSS 5.9 (Medium) reflects the network access requirement and conditional impact (integrity without availability or confidentiality loss in the base scenario).

Remediation

Upgrade pgjdbc to version 42.7.12 or later. This is a direct, version-specific fix with no configuration workarounds. If immediate upgrade is not feasible, applications that do not require channel binding should remove or set channelBinding=prefer (the default) rather than channelBinding=require, though this sacrifices the intended protection. For sensitive deployments, network segmentation and trusted network paths reduce the feasibility of MITM attacks independent of the driver fix.

Patch guidance

Pgjdbc 42.7.12 is the fixed version. Check your Maven pom.xml, Gradle build file, or equivalent dependency manager for the current version and update to 42.7.12 or any subsequent stable release. If you use a downstream distribution (e.g., through Spring Boot's dependency management or a Linux package manager), verify that the updated version is available and apply it. Test the upgrade in a non-production environment first to confirm compatibility with your PostgreSQL server version and application code.

Detection guidance

Review your application's pgjdbc dependency: extract the version from your build artifacts, class path, or dependency list (e.g., grep for org.postgresql:postgresql or check java -version + jar -tf output). Check connection strings or configuration files for channelBinding=require settings. Monitor for authentication errors or connection drops if an attacker is actively exploiting this; however, the silent downgrade means normal operation may persist even under attack. If forensic analysis is needed, enable JDBC driver logging (loglevel=DEBUG) on test systems to observe negotiated mechanisms and channel-binding headers, though production logging of credentials should follow your security policy.

Why prioritize this

Although CVSS is Medium (5.9), this vulnerability warrants prompt attention because: (1) it silently downgrades security, making it invisible to operators; (2) it requires explicit, often manually-configured, channelBinding=require settings, suggesting it affects security-conscious deployments; (3) pgjdbc is widely used in enterprise Java applications; (4) the fix is version-specific and non-disruptive. Organizations that have intentionally set channelBinding=require should treat this as a configuration-integrity issue and prioritize patching within their normal update cycles.

Risk score, explained

CVSS 5.9 rates this as Medium severity. The network-accessible attack vector and conditional prerequisite (attacker MITM position) prevent a higher base score. However, the integrity impact is high (potential for undetected query manipulation or credential interception), and the silent nature of the downgrade compounds operational risk. For organizations with strict network segmentation or where PostgreSQL is accessed over private networks, risk is lower; for those accessing databases over the internet or untrusted networks, effective risk is elevated despite the CVSS score.

Frequently asked questions