CVE-2025-49146

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

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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2025-49146 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (42.7.7); upgrading removes the vulnerable code path.

Kodem intelligence

TBD

1. What is CVE-2025-49146? CVE-2025-49146 is a high-severity improper authentication vulnerability in org.postgresql:postgresql (maven), affecting versions >= 42.7.4, < 42.7.7. It is fixed in 42.7.7. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2025-49146? CVE-2025-49146 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.postgresql:postgresql are affected by CVE-2025-49146? org.postgresql:postgresql (maven) versions >= 42.7.4, < 42.7.7 is affected.
4. Is there a fix for CVE-2025-49146? Yes. CVE-2025-49146 is fixed in 42.7.7. Upgrade to this version or later.
5. Is CVE-2025-49146 exploitable, and should I be worried? Whether CVE-2025-49146 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-49146 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-49146? Upgrade org.postgresql:postgresql to 42.7.7 or later.