CVE-2026-107314
Description
A flaw was found in the PostgreSQL JDBC Driver (pgjdbc), which may lead to information disclosure. When the requireAuth connection property is configured to exclude all supported authentication mechanisms or lacks a valid method, the driver fails to enforce authentication restrictions and accepts any method requested by the server. A man-in-the-middle attacker positioned between the application and the database server can exploit this flaw by requesting cleartext password authentication to intercept database credentials.
Statement
This vulnerability is evaluated as a Moderate severity flaw rather than Important because successful exploitation requires both an uncommon configuration and a man-in-the-middle network position. By default, the requireAuth property is unset in standard deployments, leaving applications secure in standard configurations. The failure to enforce authentication restrictions only manifests when administrators explicitly configure requireAuth to negate all known authentication mechanisms or supply invalid syntax. Furthermore, capturing database credentials necessitates an active adversary situated to intercept and manipulate client-to-server database network traffic.
Mitigation
To mitigate this issue, ensure database connection configurations do not use empty values or negation lists that exclude all supported authentication mechanisms in the `requireAuth` property. Instead, configure an explicit allowlist specifying only approved authentication methods (such as `requireAuth=scram-sha-256`) or omit the property entirely if default driver behavior is acceptable.
Additionally, protect connection traffic against man-in-the-middle interception by configuring TLS/SSL with full certificate validation on the JDBC connection string (for example, setting `sslmode=verify-full`).
Caveat: Ensure the PostgreSQL server is configured to support the chosen authentication method and SSL requirements before altering client connection parameters. Modifying connection properties in application configuration files requires restarting the affected application service.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality
Technical Impact: Read Application Data; Modify Files or Directories
Anyone can read the information by gaining access to the channel being used for communication. Many communication channels can be "sniffed" (monitored) by adversaries during data transmission. For example, in networking, packets can traverse many intermediary nodes from the source to the destination, whether across the internet, an internal network, the cloud, etc. Some actors might have privileged access to a network interface or any link along the channel, such as a router, but they might not be authorized to collect the underlying data. As a result, network traffic could be sniffed by adversaries, spilling security-critical data.
Integrity,Confidentiality
Technical Impact: Read Application Data; Modify Files or Directories; Other
When full communications are recorded or logged, such as with a packet dump, an adversary could attempt to obtain the dump long after the transmission has occurred and try to "sniff" the cleartext from the recorded communications in the dump itself. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
