[ CVE-2026-107315 · Published 8 Oct 2026 ]

Vulnerability in pgjdbc

CVSS 5.3 EPSS <1%2 agency advisoriesFix available

[ Why it matters ]Priority signals

  • Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

[ Advisories ]Government CERT advisories

  • CERT-FRCERTFR-2026-AVI-1292

    Multiple vulnerabilities in PostgreSQL JDBC Translated from French

    Multiple vulnerabilities have been discovered in PostgreSQL JDBC. They allow an attacker to cause a breach of data confidentiality and a security policy bypass.

    CVE-2026-107315CVE-2026-107314
  • BSI CERT-BundWID-SEC-2026-3807

    PostgreSQL JDBC Driver: Multiple vulnerabilities Translated from German

    CVE-2026-107315CVE-2026-107314CVE-2026-107313