CVE-2025-49146: pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration

Published Jun 11, 2025
·
Updated

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

https://www.postgresql.org/docs/current/sasl-authentication.html#SASL-SCRAM-SHA-256 https://datatracker.ietf.org/doc/html/rfc7677 https://datatracker.ietf.org/doc/html/rfc5802

Other sources

pgjdbc is an open source postgresql JDBC Driver. From 42.7.4 and until 42.7.7, 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. This vulnerability is fixed in 42.7.7.

NVD

Affected Software

3 affected componentsFixes available
maven/org.postgresql:postgresql>=42.7.4<42.7.7
42.7.7
PostgreSQL PostgreSQL JDBC driver>=42.7.4<42.7.7
IBM Concert Software<=1.0.0-2.1.0

Event History

Jun 11, 2025
CVE Published
via MITRE·02:32 PM
Data Sourced
via MITRE·02:32 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·02:44 PM
Data Sourced
via GitHub·02:44 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·03:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyAffected Software
Dec 22, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-49146?

CVE-2025-49146 is considered a medium severity vulnerability due to its potential impact on secure connections in PostgreSQL JDBC driver configurations.

2

How do I fix CVE-2025-49146?

To fix CVE-2025-49146, update the PostgreSQL JDBC driver to version 42.7.8 or higher, which addresses the channel binding misconfiguration.

3

What configurations are affected by CVE-2025-49146?

CVE-2025-49146 affects PostgreSQL JDBC driver configurations specifically when channel binding is set to 'required'.

4

What authentication methods are incompatible with channel binding in CVE-2025-49146?

CVE-2025-49146 outlines that authentication methods like password, MD5, GSS, and SSPI do not support channel binding when required.

5

Is CVE-2025-49146 a common vulnerability in PostgreSQL setups?

CVE-2025-49146 may occur in PostgreSQL setups that have the JDBC driver incorrectly configured for channel binding, making it important for users to verify their configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203