Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgdfb-006J1g-1g for pgsql-announce@arkaria.postgresql.org; Mon, 06 Jul 2026 07:23:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgdfa-00FZiy-1D for pgsql-announce@arkaria.postgresql.org; Mon, 06 Jul 2026 07:23:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgdfZ-00FZio-1g for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 07:23:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wgdfW-000000020ow-1g92 for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 07:23:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=xH39SqCwZxYLJ3xIs10fJJQnugua5XFS9gezoOo1QAQ=; b=q3Q0peK8FVKADjD07R6zO2yVGv +LZu/Eg6wU8EQ9PB6eGZHocA91eQSOvvFY7GdW68cuDs8Y2rlmesmI5o2yVU3wxdwiB/bx8Vd2qlq yqmDWR/oZ3LyIj3KcBfb7Bua0SQayfxTXxxkXtPIdF8YuWMTeJXu2KoV0xsY2KOEs3scXwrNahp/V HAVhAqxy83sBxOLIfCsq4D5Y0nuuvuNhUxZvs5gbzhvgv6eaAYp6ogAF6df1RtscmGa5/bFc1OHoo zIQnu5Yv9qJQ6rMv+Be8ddBK3HMhtGbIyjcUQBg45nONpOHnZvKFOdzzV692H5fdgw1zXgy+iDJSl JzxpJE2Q==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgdfU-00BRw2-3C for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 07:23:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgdfT-00Dz7e-1i for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 07:23:03 +0000 Content-Type: multipart/alternative; boundary="===============2066727285324764329==" MIME-Version: 1.0 Subject: PostgreSQL JDBC 42.7.12 Security Release To: PostgreSQL Announce From: JDBC Project via PostgreSQL Announce Reply-To: davec@postgres.rocks Date: Mon, 06 Jul 2026 07:23:02 +0000 Message-ID: <178332258247.108994.12124505900952045249@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary,security X-pglister-tagsig: 49be8081b8301df3cb6a84f39d72a0dabbff9a480a27ef195f453f322c56a050 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============2066727285324764329== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Silent channel-binding authentication downgrade (CVE-2026-54291) channelBinding=3Drequire connections can be silently downgraded from SCRAM-= SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), lo= sing the man-in-the-middle protection the setting is meant to guarantee. An= attacker who can intercept the TLS connection triggers the downgrade with = a certificate whose signature algorithm has no tls-server-end-point channel= -binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms. Two issues combine in releases 42.7.4 through 42.7.11: The bundled com.ongres.scram:scram-client (3.1 or 3.2) returns an empty byt= e array instead of failing when it cannot derive the binding hash for such = a certificate. This is the library issue tracked as [GHSA-p9jg-fcr6-3mhf](h= ttps://github.com/ongres/scram/security/advisories/GHSA-p9jg-fcr6-3mhf). pgJDBC does not enforce channelBinding=3Drequire where it matters. ScramAut= henticator checks only that the server advertised a -PLUS mechanism; it nei= ther rejects the empty binding nor checks that the negotiated mechanism use= s channel binding. The connection therefore downgrades silently. Only connections that set channelBinding=3Drequire are affected. Under the = default prefer policy, and under allow or disable, falling back to plain SC= RAM is the documented behaviour. Releases before 42.7.4 are unaffected, because they do not support channel = binding. --===============2066727285324764329== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PostgreSQL JDBC 42.7.12 Security Release
 

PostgreSQL JDBC 42.7.12 Security Release

Silent channel-binding authentication downg= rade (CVE-2026-54291) channelBinding=3Drequire connections can be silently downgraded from SCRAM-= SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), lo= sing the man-in-the-middle protection the setting is meant to guarantee. An= attacker who can intercept the TLS connection triggers the downgrade with = a certificate whose signature algorithm has no tls-server-end-point channel= -binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms.

Two issues combine in releases 42.7.4 throu= gh 42.7.11:

The bundled com.ongres.scram:scram-client (= 3.1 or 3.2) returns an empty byte array instead of failing when it cannot d= erive the binding hash for such a certificate. This is the library issue tr= acked as GHSA= -p9jg-fcr6-3mhf.

pgJDBC does not enforce channelBinding=3Dre= quire where it matters. ScramAuthenticator checks only that the server adve= rtised a -PLUS mechanism; it neither rejects the empty binding nor checks t= hat the negotiated mechanism uses channel binding. The connection therefore= downgrades silently.

Only connections that set channelBinding=3D= require are affected. Under the default prefer policy, and under allow or d= isable, falling back to plain SCRAM is the documented behaviour.

Releases before 42.7.4 are unaffected, beca= use they do not support channel binding.
This email was sent to you from JDBC Project. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to JDBC Project.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for for one of the content tags Related Proprietary or Security. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============2066727285324764329==--