Bug 2547744 (CVE-2026-107315)

Summary: CVE-2026-107315 org.postgresql/postgresql: PostgreSQL JDBC Driver: Information disclosure via residual send buffer padding
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: anthomas, ant, aschwart, asyoung, aszczucz, ataylor, boliveir, ccranfor, cescoffi, cmah, csuconic, dbruscin, drichtar, eglynn, ehelms, ehugonne, ewittman, fmongiar, ggainey, gmalinko, gsmet, gtully, janstey, jhollowa, jjoyce, jmartisk, jpasqual, jpechane, jpretori, jschluet, jsherman, juwatts, kaycoth, kvanderr, lhh, manderse, mburns, mdellweg, mgarciac, mhulan, mposolda, nipatil, nmoumoul, olubyans, osousa, ozzy, pantinor, pcreech, pdelbell, pjindal, prichard, rchan, rgemmell, rgodfrey, rguimara, rhel-process-autobot, rkubis, rmartinc, rstepani, sbiarozk, sdawley, smallamp, ssilvert, sthirugn, sthorger, tbish, tlavocat, tmalecek, varjain, vmuzikar, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the PostgreSQL JDBC Driver (pgjdbc). When an application transmits a value shorter than its declared length, the driver pads the remaining data with residual bytes from its internal send buffer instead of zero bytes. An attacker who can induce the application to store and subsequently retrieve such data can access sensitive information, including previously executed database queries and parameters from earlier transactions on pooled connections.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-10-07 23:31:23 UTC
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.