CVE-2026-42198
HIGHEPSS 91th pctlDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
High risk: more likely to be exploited than 91% of all known CVEs.
References
Related Vulnerabilities
Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-50387 | High | 7.5 | 100% | - | Fix |
| CVE-2019-11478 | Medium | 5.3 | 95% | - | Fix |
| CVE-2019-11479 | High | 7.5 | 92% | - | Fix |
| CVE-2024-27316 | High | 7.5 | 91% | - | Fix |
| CVE-2022-30522 | High | 7.5 | 90% | - | Fix |
| CVE-2019-9515 | High | 7.5 | 87% | - | Fix |
Common questions
How do I fix CVE-2026-42198?
Published advisories record a fix for 5 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-42198 being actively exploited?
Not that we know of. CVE-2026-42198 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 4.1% is the estimated probability that it will be exploited in the next 30 days. That is higher than 91% of all scored CVEs.
How severe is CVE-2026-42198?
CVE-2026-42198 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-42198 affect?
Published advisories record a fix for libpgjava (Debian), postgresql-jdbc (Red Hat / RHEL), postgresql-jdbc (Rocky), postgresql-jdbc-javadoc (Red Hat / RHEL), and 1 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-42198
Markdown
[](https://tridentstack.com/cve/CVE-2026-42198)HTML
<a href="https://tridentstack.com/cve/CVE-2026-42198"><img src="https://tridentstack.com/cve/badge/CVE-2026-42198.svg" alt="CVE-2026-42198"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-11.