CVE-2026-107314

pgjdbc does not enforce requireAuth when the value excludes every authentication method

Published Oct 7, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.11 through 42.7.13 enforce no restriction when the requireAuth connection property excludes all six authentication methods the driver knows, for example requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none. The driver then accepts any method the server asks for, including cleartext password authentication. A value without a method in it, such as requireAuth=, (a single comma), is affected the same way. An attacker positioned between the application and its server can ask for cleartext password authentication and receive the database password. A positive list such as requireAuth=scram-sha-256, and a partial exclusion such as requireAuth=!password,!md5, are enforced correctly. The property has no default value, so a deployment that does not set it is not affected. 42.7.14 fixes the problem: such a connection is refused with SQLState 08004, and a value without a method in it is rejected as invalid.

Analysis

AI-generated

Technical impact

The PostgreSQL JDBC driver silently accepts authentication methods it should reject when the requireAuth property excludes every known method or is empty. As a result, an attacker between the application and the server can force the driver to accept cleartext password authentication and retrieve the database password, producing a cleartext credential disclosure that undermines database confidentiality.

Affected Systems

The vulnerability affects the PostgreSQL JDBC Driver (pgjdbc) versions 42.7.11 through 42.7.13 when the connection property requireAuth is set to exclude all authentication methods or to an empty value. No other pgjdbc versions or products are affected. The driver has no default value for requireAuth, so systems that do not set the property are not impacted.

Risk and Exploitability

The CVSS base score is 5.9, reflecting a moderate severity. The EPSS score is 0.00256 (0.256%) and the issue is not listed in CISA’s KEV catalogue, suggesting no publicly confirmed exploitation. However, the attack requires an attacker to position themselves between the application and database server and to initiate a cleartext password authentication request. Once the driver is tricked, it will transmit the password in cleartext to the attacker, granting credential theft. Although exploitation conditions are relatively specific, the potential impact on confidentiality is significant.

Remediation

Vendor Solution

Upgrade to pgjdbc 42.7.14 or later, and replace a requireAuth value that excludes every method or names none with a positive list of the methods the server uses.


Vendor Workaround

Replace the requireAuth value with a positive list of the methods the server uses, for example requireAuth=scram-sha-256; a positive list is enforced correctly on every affected version. A deployment that uses SCRAM over TLS can also set channelBinding=require, which refuses every authentication request other than SCRAM. Verifying the server certificate with sslmode=verify-full against a trusted CA prevents an attacker from presenting a substitute server.


OpenCVE Recommended Actions

  • Upgrade the PostgreSQL JDBC driver to 42.7.14 or later, which rejects connections with invalid requireAuth settings.
  • Replace any requireAuth value that excludes all methods or is empty with a positive whitelist such as requireAuth=scram-sha-256.
  • If SCRAM over TLS is used, set channelBinding=require so that only SCRAM authentication is accepted, and configure sslmode=verify-full to enforce proper server certificate validation.

Generated by OpenCVE AI on October 9, 2026 at 02:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Pgjdbc
Pgjdbc pgjdbc
Vendors & Products Pgjdbc
Pgjdbc pgjdbc
Type Values Removed Values Added
Description pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.11 through 42.7.13 enforce no restriction when the requireAuth connection property excludes all six authentication methods the driver knows, for example requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none. The driver then accepts any method the server asks for, including cleartext password authentication. A value without a method in it, such as requireAuth=, (a single comma), is affected the same way. An attacker positioned between the application and its server can ask for cleartext password authentication and receive the database password. A positive list such as requireAuth=scram-sha-256, and a partial exclusion such as requireAuth=!password,!md5, are enforced correctly. The property has no default value, so a deployment that does not set it is not affected. 42.7.14 fixes the problem: such a connection is refused with SQLState 08004, and a value without a method in it is rejected as invalid.
Title pgjdbc does not enforce requireAuth when the value excludes every authentication method
Weaknesses CWE-636
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-319

    Cleartext Transmission of Sensitive Information

  • CWE-636

    Not Failing Securely ('Failing Open')

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Oct 8, 2026, 2:47 PM
Reserved
Oct 7, 2026, 4:53 PM
Status
Awaiting Analysis
Published
Oct 7, 2026, 11:17 PM
Modified
Oct 8, 2026, 8:49 PM
Severity
Moderate
Public date
Oct 7, 2026, 11:03 PM