pgjdbc up to 42.7.13 Connection Pool PreparedStatement.setObject length information disclosure

Summaryinfo

A vulnerability marked as problematic has been reported in pgjdbc up to 42.7.13. Affected by this vulnerability is the function PreparedStatement.setObject of the component Connection Pool. This manipulation of the argument length causes information disclosure. This vulnerability is registered as CVE-2026-107315. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in pgjdbc up to 42.7.13. It has been declared as problematic. Affected by this vulnerability is the function PreparedStatement.setObject of the component Connection Pool. The manipulation of the argument length with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 through 42.7.13 pads a value that is shorter than its declared length with bytes left in its send buffer instead of zeros, and the server stores those bytes as part of the value. The bytes are messages the driver sent earlier on the same connection: SQL text and parameter values of recent statements, which on a pooled connection can come from other requests. Each padded value can carry up to 8192 bytes of this traffic, or 16320 bytes on a connection with GSS encryption. The padding happens when an application declares a length larger than the data it supplies, through PreparedStatement.setObject with a ByteStreamWriter, CopyIn.writeToCopy, PGCopyOutputStream.write, LargeObject.write, or Blob.setBytes. The driver accepts these calls without an error. An attacker who can make the application store such a value and read it back can collect earlier traffic. Applications whose declared lengths always match their data are not affected. Versions 42.7.3 and earlier pad with zeros.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-107315 since 10/07/2026. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• pgjdbc

Version

• 42.7.0
• 42.7.1
• 42.7.2
• 42.7.3
• 42.7.4
• 42.7.5
• 42.7.6
• 42.7.7
• 42.7.8
• 42.7.9
• 42.7.10
• 42.7.11
• 42.7.12
• 42.7.13

Website

• Product: https://github.com/pgjdbc/pgjdbc/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion