Skip to content
Fencer Vulns
medium 5.3

CVE-2026-107315 json

pgjdbc pads a value shorter than its declared length with bytes of earlier statements (rather than zeros)

published 2026-10-07 32 d ago modified 2026-10-08 31 d ago also EUVD-2026-94650

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

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.

Patch / fix

  • libpgjava Debian 14 42.7.14-1

debian advisories DEBIAN-CVE-2026-107315

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-107315 updated cvss 5.3

org.postgresql/postgresql: PostgreSQL JDBC Driver: Information disclosure via residual send buffer padding

  • Red Hat AMQ Broker 7 postgresql Red Hat build of Apicurio Registry 3 postgresql Red Hat build of Debezium 3 postgresql Red Hat Build of Keycloak postgresql, rhbk/keycloak-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Quarkus postgresql
    affected: workaround, no fix available
  • Red Hat OpenShift Dev Spaces devspaces/server-rhel9, devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Satellite 6 candlepin, candlepin-selinux
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 Judy, galera, mariadb, mariadb-pam, mariadb-test, mariadb-backup, +10 more Red Hat Enterprise Linux 9 postgresql-jdbc Red Hat Enterprise Linux 10 postgresql-jdbc Red Hat Fuse 7 postgresql
    not affected: vulnerable code not present
  • Red Hat Hardened Images mariadb10.11 10.11.18-4.hum1
    not affected: component not present
  • Red Hat OpenStack Platform 13 (Queens) mariadb, mariadb-libs, mariadb-test, mariadb-common, mariadb-config, mariadb-errmsg, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
31 d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-f64h-wr5q-3qf3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

  • pgjdbc pgjdbc

Classification

Weakness
  • CWE-226 Sensitive Information in Resource Not Removed Before Reuse
  • CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.