libpgjava updated to version 42.7.14-1.pgdg+1

The package libpgjava was updated on apt.postgresql.org.

apt-listchanges: Changelogs
---------------------------

libpgjava (42.7.14-1.pgdg+1) sid-pgdg; urgency=medium

* Rebuild for sid-pgdg.
* No source changes.

-- PostgreSQL on Debian and Ubuntu <pgsql-pkg-debian(at)lists(dot)postgresql(dot)org> Fri, 09 Oct 2026 11:14:28 +0200

libpgjava (42.7.14-1) unstable; urgency=medium

* New upstream version 42.7.14. (Closes: #1150330)
+ CVE-2026-107315: versions 42.7.4 through 42.7.13 pad 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.
+ CVE-2026-107314: versions 42.7.11 through 42.7.13 enforce no restriction
when the requireAuth connection property excludes all six authentication
methods the driver knows, for example
requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none. The driver
then accepts any method the server asks for, including cleartext
password authentication. A value without a method in it, such as
requireAuth=, (a single comma), is affected the same way. An attacker
positioned between the application and its server can ask for cleartext
password authentication and receive the database password. A positive
list such as requireAuth=scram-sha-256, and a partial exclusion such as
requireAuth=!password,!md5, are enforced correctly. The property has no
default value, so a deployment that does not set it is not affected.
42.7.14 fixes the problem: such a connection is refused with SQLState
08004, and a value without a method in it is rejected as invalid.

-- Christoph Berg <myon(at)debian(dot)org> Fri, 09 Oct 2026 11:14:28 +0200

New version 42.7.14-1.pgdg+1:

libpgjava | 42.7.14-1.pgdg+1 | sid-pgdg | source
libpgjava | 42.7.13-1.pgdg+1 | sid-pgdg | source
libpgjava | 42.7.12-1.pgdg+1 | sid-pgdg | source
libpgjava | 42.7.14-1.pgdg14+1 | forky-pgdg | source
libpgjava | 42.7.13-1.pgdg14+1 | forky-pgdg | source
libpgjava | 42.7.12-1.pgdg14+1 | forky-pgdg | source
libpgjava | 42.7.14-1.pgdg13+1 | trixie-pgdg | source
libpgjava | 42.7.13-1.pgdg13+1 | trixie-pgdg | source
libpgjava | 42.7.12-1.pgdg13+1 | trixie-pgdg | source
libpgjava | 42.7.14-1.pgdg12+1 | bookworm-pgdg | source
libpgjava | 42.7.13-1.pgdg12+1 | bookworm-pgdg | source
libpgjava | 42.7.12-1.pgdg12+1 | bookworm-pgdg | source
libpgjava | 42.7.14-1.pgdg26.10+1 | stonking-pgdg | source
libpgjava | 42.7.13-1.pgdg26.10+1 | stonking-pgdg | source
libpgjava | 42.7.14-1.pgdg26.04+1 | resolute-pgdg | source
libpgjava | 42.7.13-1.pgdg26.04+1 | resolute-pgdg | source
libpgjava | 42.7.12-1.pgdg26.04+1 | resolute-pgdg | source
libpgjava | 42.7.14-1.pgdg24.04+1 | noble-pgdg | source
libpgjava | 42.7.13-1.pgdg24.04+1 | noble-pgdg | source
libpgjava | 42.7.12-1.pgdg24.04+1 | noble-pgdg | source
libpgjava | 42.7.14-1.pgdg22.04+1 | jammy-pgdg | source
libpgjava | 42.7.13-1.pgdg22.04+1 | jammy-pgdg | source
libpgjava | 42.7.12-1.pgdg22.04+1 | jammy-pgdg | source
libpostgresql-jdbc-java | 42.7.14-1.pgdg+1 | sid-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg+1 | sid-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg+1 | sid-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg14+1 | forky-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg14+1 | forky-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg14+1 | forky-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg13+1 | trixie-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg13+1 | trixie-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg13+1 | trixie-pgdg | amd64, arm64, loong64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg12+1 | bookworm-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg12+1 | bookworm-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg12+1 | bookworm-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg26.10+1 | stonking-pgdg | amd64
libpostgresql-jdbc-java | 42.7.13-1.pgdg26.10+1 | stonking-pgdg | amd64
libpostgresql-jdbc-java | 42.7.14-1.pgdg26.04+1 | resolute-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg26.04+1 | resolute-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg26.04+1 | resolute-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg24.04+1 | noble-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg24.04+1 | noble-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg24.04+1 | noble-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.14-1.pgdg22.04+1 | jammy-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.13-1.pgdg22.04+1 | jammy-pgdg | amd64, arm64, ppc64el
libpostgresql-jdbc-java | 42.7.12-1.pgdg22.04+1 | jammy-pgdg | amd64, arm64, ppc64el

The public mirrors serving apt.postgresql.org are synced hourly,
the updated packages will be available there shortly.