Bug 2463857 (CVE-2026-42198) - CVE-2026-42198 jdbc.postgresql.org: pgjdbc: Client-side Denial of Service via malicious SCRAM-SHA-256 authentication
Summary: CVE-2026-42198 jdbc.postgresql.org: pgjdbc: Client-side Denial of Service via...
Keywords:
Status: NEW
Alias: CVE-2026-42198
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2466758
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-29 17:01 UTC by OSIDB Bzimport
Modified: 2026-06-01 10:09 UTC (History)
23 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:22304 0 None None None 2026-06-01 10:09:44 UTC

Description OSIDB Bzimport 2026-04-29 17:01:22 UTC
pgjdbc is an open source postgresql JDBC Driver. From version 42.2.0 to before version 42.7.11, pgjdbc is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication. A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count. With a large enough value, the client spends an unbounded amount of CPU time inside PBKDF2 before authentication can fail. A single attempt ties up a CPU core. Repeated or concurrent attempts exhaust client CPU and can wedge connection pools. In affected versions, loginTimeout did not fully mitigate this problem. When loginTimeout expired, the caller could stop waiting, but the worker thread performing the connection attempt could continue running and burning CPU inside the SCRAM PBKDF2 computation. This issue has been patched in version 42.7.11.

Comment 3 errata-xmlrpc 2026-06-01 10:09:42 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:22304 https://access.redhat.com/errata/RHSA-2026:22304


Note You need to log in before you can comment on or make changes to this bug.