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.
CVE-2026-42198
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 3.3% (88th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-26247 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 50EG Risk 50/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation3.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 3.3%
- EPSS %ILE
- 88th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 3.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
April 29, 2026
Last Modified
September 11, 2026
Advisory Details (2)
Auto-updated Apr 29, 2026Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS · Advisory · pgjdbc/pgjdbc · GitHub
https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-98qh-xjc8-98pqRelease v42.7.11 · pgjdbc/pgjdbc · GitHub
https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.11Vendor Advisories for CVE-2026-42198(13)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:66545Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AMQ Broker 7.13.6 release and security update
- RHSA-2026:66488Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AMQ Broker 7.14.1 release and security update
- RHSA-2026:59277Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2026:59278Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2026:54532Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2026:52978Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2026:52930Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2026:52929Red Hat Product SecurityHigh
Red Hat Security Advisory: postgresql-jdbc security update
- +5 more
Patch Availability(12)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | postgresql | 2026-09-10 | redhat |
| redhat | postgresql-jdbc-0:42.2.3-7.el8_4.1 | 2026-08-25 | redhat |
| redhat | postgresql-jdbc-0:42.2.3-5.el8_6.1 | 2026-08-25 | redhat |
| redhat | postgresql-jdbc-0:42.2.28-1.el9_2.1 | 2026-08-13 | redhat |
| redhat | postgresql-jdbc-0:42.2.28-1.el9_6.1 | 2026-08-10 | redhat |
| redhat | postgresql-jdbc-0:42.7.1-7.el10_0.1 | 2026-08-10 | redhat |
| redhat | postgresql-jdbc-0:42.2.14-5.el8_8.1 | 2026-08-10 | redhat |
| redhat | postgresql-jdbc-0:42.2.28-1.el9_4.1 | 2026-08-10 | redhat |
| redhat | postgresql-jdbc-0:42.2.14-4.el8_10 | 2026-06-10 | redhat |
| redhat | postgresql-jdbc-0:42.7.2-1.el10_2.2 | 2026-06-08 | redhat |
| redhat | postgresql-jdbc-0:42.2.28-2.el9_8.2 | 2026-06-01 | redhat |
| redhat | org.postgresql/postgresql:42.7.11.redhat-00001 | 2026-05-20 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.2.15-1 ... 42.7.9-1 (39 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.5.4-1 ... 42.7.9-1 (21 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.7.10-1 ... 42.7.9-1 (9 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.7.10-1 ... 42.7.9-1 (6 versions) |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.postgresql:postgresql | 42.2.0 ... 42.7.9 (125 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 36× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 249 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 149 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-25 14:29 UTCEG score recompute
- 2026-10-25 04:07 UTCEG score recompute
- 2026-10-25 04:07 UTCVendor advisory
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-18 03:41 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-17 14:29 UTCEG score recompute
- 2026-10-17 14:29 UTCVendor advisory
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 3.3% · 88th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-12 16:07 UTCEG score recompute
- 2026-10-11 19:49 UTCEG score recompute
- 2026-10-11 17:03 UTCEG score recompute
- 2026-10-11 14:29 UTCEG score recompute
Show 75 moreShow fewer
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-09-30 07:28 UTCOSV refresh
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 4.1% · 90th percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-12 15:01 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-11 13:25 UTCEG score recompute
- 2026-09-11 13:25 UTCVendor advisory
- 2026-09-11 12:21 UTCEG score recompute
- 2026-09-11 12:21 UTCVendor advisory
- 2026-09-11 09:37 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-05 01:44 UTCOSV refresh
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-18 12:19 UTCEG score recompute
- 2026-08-18 12:19 UTCVendor advisory
- 2026-08-17 13:54 UTCEG score recompute
- 2026-08-17 13:54 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 3.3% · 87th percentile
- 2026-08-16 05:26 UTCEG score recompute
- 2026-08-16 05:26 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-08-15 02:26 UTCEG score recompute
- 2026-08-15 02:26 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-08-14 13:28 UTCEG score recompute
- 2026-08-14 13:28 UTCVendor advisory
- 2026-08-14 12:29 UTCEG score recompute
- 2026-08-14 12:29 UTCVendor advisory
- 2026-08-14 03:53 UTCEG score recompute
- 2026-08-14 03:53 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-08-13 08:21 UTCVendor advisory
- 2026-08-12 17:31 UTCEG score recompute
- 2026-08-12 17:31 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
- 2026-08-12 02:22 UTCEG score recompute
- 2026-08-12 02:22 UTCVendor advisory
- 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
- 2026-08-11 13:23 UTCEG score recompute
- 2026-08-11 13:23 UTCVendor advisory
- 2026-08-11 12:24 UTCVendor advisory
- 2026-08-11 01:54 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:libpgjava · Maven:org.postgresql:postgresql · Debian:12:libpgjava
Same vendor
10 shownredhat:RHSA-2026:66488
Frequently asked(5)
What is CVE-2026-42198?
When was the CVE record for CVE-2026-42198 published?
Is CVE-2026-42198 actively exploited?
What is the CVSS score of CVE-2026-42198?
How do I remediate CVE-2026-42198?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42198
Is Your Infrastructure Affected by CVE-2026-42198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.