Skip to content

pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration

High severity GitHub Reviewed Published Jun 11, 2025 in pgjdbc/pgjdbc • Updated Jun 11, 2025

Package

maven org.postgresql:postgresql (Maven)

Affected versions

>= 42.7.4, < 42.7.7

Patched versions

42.7.7

Description

Impact

When the PostgreSQL JDBC driver is configured with channel binding set to required (default value is prefer), the driver would incorrectly allow connections to proceed with authentication methods that do not support channel binding (such as password, MD5, GSS, or SSPI authentication). This could allow a man-in-the-middle attacker to intercept connections that users believed were protected by channel binding requirements.

Patches

TBD

Workarounds

Configure sslMode=verify-full to prevent MITM attacks.

References

References

@davecramer davecramer published to pgjdbc/pgjdbc Jun 11, 2025
Published to the GitHub Advisory Database Jun 11, 2025
Reviewed Jun 11, 2025
Published by the National Vulnerability Database Jun 11, 2025
Last updated Jun 11, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(5th percentile)

Weaknesses

Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Learn more on MITRE.

CVE ID

CVE-2025-49146

GHSA ID

GHSA-hq9p-pm7w-8p54

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.