From: jphalip (@jphalip) <noreply+jphalip@github.com>
To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>
Subject: [pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners
Date: Mon, 16 Nov 2026 19:08:37 +0000
Message-ID: <gh-pgjdbc-pgjdbc-4532@github.com> (raw)
Hello there. Our vulnerability scanners are flagging 42.7.14 because it shades `com.ongres.scram:scram-client` and `scram-common` 3.2, which are affected by [GHSA-p9jg-fcr6-3mhf](https://github.com/advisories/GHSA-p9jg-fcr6-3mhf) (CVE-2026-53712, fixed in 3.3).
We know 42.7.12 already fixes the downgrade in the driver itself (GHSA-j92g-9f8w-j867, #4272), independently of the scram-client version. Unfortunately, the scanners only compare library versions, so the jar is blocked in our release pipelines until a release bundles scram 3.3 or later.
We saw that #4298 was closed and that #4428 keeps minor ongres bumps for pgJDBC minor releases. Given that this is a security advisory, would you consider an exception for 42.7.15? If not, is there a rough date for the next minor release?
We're happy to send the PR. From a quick look, it would bump scram-client to 3.4 (3.3 has a regression that 3.4 fixes) and stringprep/saslprep to 2.4, and replace the deprecated `TlsServerEndpoint.getChannelBindingData` in `ScramAuthenticator`, which currently fails the build under `-Werror`, with `getChannelBindingHash`. scram 3.4 still targets Java 8. Let us know which branch you'd want it against.
Thanks!