CVE-2026-42198: pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: pgjdbc pgjdbc 42.7.11.
Low priority for now. Upgrade to pgjdbc pgjdbc 42.7.11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-10803
- GHSA-98qh-xjc8-98pq
- ALSA-2026:22304
- ALSA-2026:24348
- ALSA-2026:25030
- openSUSE-SU-2026:11001-1
- RHSA-2026:22304
- RHSA-2026:24348
- RHSA-2026:25030
- RHSA-2026:52928
- RHSA-2026:52929
- RHSA-2026:52930
- RHSA-2026:52978
- RHSA-2026:54532
- RHSA-2026:59277
- RHSA-2026:59278
- RLSA-2026:22304
- RLSA-2026:24348
- RLSA-2026:25030
- SUSE-SU-2026:22000-1
- Published
- Apr 29, 2026
- Updated
- Nov 11, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- CWE-770
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql jdbc driver | cpe:2.3:a:postgresql:postgresql_jdbc_driver |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
pgjdbc pgjdbc
- >= 42.2.0, < 42.7.11affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql jdbc driver42.2.0 and later · before 42.7.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | postgresql-jdbc | before 42.7.2-1.el10_2.2 | 42.7.2-1.el10_2.2 |
| AlmaLinux:8 | postgresql-jdbc | before 42.2.14-4.el8_10 | 42.2.14-4.el8_10 |
| AlmaLinux:8 | postgresql-jdbc-javadoc | before 42.2.14-4.el8_10 | 42.2.14-4.el8_10 |
| AlmaLinux:9 | postgresql-jdbc | before 42.2.28-2.el9_8.2 | 42.2.28-2.el9_8.2 |
| Debian:12 | libpgjava | from 0 | — |
| Debian:14 | libpgjava | before 42.7.11-1 | 42.7.11-1 |
| Maven | org.postgresql:postgresql | from 42.2.0 · before 42.7.11 | 42.7.11 |
| openSUSE:Tumbleweed | postgresql-jdbc | before 42.7.11-1.1 | 42.7.11-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | postgresql-jdbc | before 0:42.7.1-7.el10_0.1 | 0:42.7.1-7.el10_0.1 |
| Red Hat:enterprise_linux:10.2 | postgresql-jdbc | before 0:42.7.2-1.el10_2.2 | 0:42.7.2-1.el10_2.2 |
| Red Hat:enterprise_linux:8::appstream | postgresql-jdbc | before 0:42.2.14-4.el8_10 | 0:42.2.14-4.el8_10 |
| Red Hat:enterprise_linux:8::appstream | postgresql-jdbc-javadoc | before 0:42.2.14-4.el8_10 | 0:42.2.14-4.el8_10 |
| Red Hat:enterprise_linux:9::appstream | postgresql-jdbc | before 0:42.2.28-2.el9_8.2 | 0:42.2.28-2.el9_8.2 |
| Red Hat:rhel_aus:8.4::appstream | postgresql-jdbc | before 0:42.2.3-7.el8_4.1 | 0:42.2.3-7.el8_4.1 |
| Red Hat:rhel_aus:8.4::appstream | postgresql-jdbc-javadoc | before 0:42.2.3-7.el8_4.1 | 0:42.2.3-7.el8_4.1 |
| Red Hat:rhel_aus:8.6::appstream | postgresql-jdbc | before 0:42.2.3-5.el8_6.1 | 0:42.2.3-5.el8_6.1 |
| Red Hat:rhel_aus:8.6::appstream | postgresql-jdbc-javadoc | before 0:42.2.3-5.el8_6.1 | 0:42.2.3-5.el8_6.1 |
| Red Hat:rhel_e4s:8.8::appstream | postgresql-jdbc | before 0:42.2.14-5.el8_8.1 | 0:42.2.14-5.el8_8.1 |
| Red Hat:rhel_e4s:8.8::appstream | postgresql-jdbc-javadoc | before 0:42.2.14-5.el8_8.1 | 0:42.2.14-5.el8_8.1 |
| Red Hat:rhel_e4s:9.2::appstream | postgresql-jdbc | before 0:42.2.28-1.el9_2.1 | 0:42.2.28-1.el9_2.1 |
| Red Hat:rhel_e4s:9.4::appstream | postgresql-jdbc | before 0:42.2.28-1.el9_4.1 | 0:42.2.28-1.el9_4.1 |
| Red Hat:rhel_eus:9.6::appstream | postgresql-jdbc | before 0:42.2.28-1.el9_6.1 | 0:42.2.28-1.el9_6.1 |
| Rocky Linux:10 | postgresql-jdbc | before 0:42.7.2-1.el10_2.2 | 0:42.7.2-1.el10_2.2 |
| Rocky Linux:8 | postgresql-jdbc | before 0:42.2.14-4.el8_10 | 0:42.2.14-4.el8_10 |
+47
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-1597pgjdbc SQL Injection via line comment generation40Plan
- CVE-2022-26520In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary…40Plan
- CVE-2022-21724Unchecked Class Instantiation when providing Plugin Classes40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-41946Nov 23, 2022 · TemporaryFolder on unix-like systems does not limit access to created files in pgjdbc22Monitor
- ← EarlierCVE-2025-49146Jun 11, 2025 · pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration23Monitor
- Later →CVE-2026-54291Jul 6, 2026 · Silent channel-binding authentication downgrade via unsupported certificate algorithms32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| pgjdbc pgjdbc | 42.7.11 · description | Vendor (CNA) |
| almalinux:postgresql-jdbc | 42.2.28-2.el9_8.2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:postgresql-jdbc-javadoc | 42.2.14-4.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:libpgjava | 42.7.11-1 · Debian:14 | Package registry (OSV) |
| Maven:org.postgresql:postgresql | 42.7.11 | Package registry (OSV) |
| opensuse:postgresql-jdbc | 42.7.11-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:postgresql-jdbc | 0:42.2.28-2.el9_8.2 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:postgresql-jdbc-javadoc | 0:42.2.14-4.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:postgresql-jdbc | 0:42.2.28-2.el9_8.2 · Rocky Linux:9 | Package registry (OSV) |
| suse:postgresql-jdbc | 42.7.7-160000.3.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-aarch64-proxy-httpd-image | 5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-aarch64-proxy-salt-broker-image | 5.1.4-9.20.25 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-aarch64-proxy-squid-image | 5.1.4-8.20.11 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-aarch64-proxy-ssh-image | 5.1.4-8.20.12 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-aarch64-proxy-tftpd-image | 5.1.4-8.20.13 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-ppc64le-proxy-httpd-image | 5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-ppc64le-proxy-salt-broker-image | 5.1.4-9.20.25 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-ppc64le-proxy-squid-image | 5.1.4-8.20.11 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-ppc64le-proxy-ssh-image | 5.1.4-8.20.12 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-ppc64le-proxy-tftpd-image | 5.1.4-8.20.13 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
| suse:suse-multi-linux-manager-5.1-s390x-proxy-httpd-image | 5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (17 more)Show less
- github.com/pgjdbc/pgjdbc/security/advisories/GHSA-98qh-xjc8-98pq
- access.redhat.com/errata/RHSA-2026:19098
- access.redhat.com/errata/RHSA-2026:22304
- access.redhat.com/errata/RHSA-2026:24348
- access.redhat.com/errata/RHSA-2026:25030
- access.redhat.com/errata/RHSA-2026:52928
- access.redhat.com/errata/RHSA-2026:52929
- access.redhat.com/errata/RHSA-2026:52930
- access.redhat.com/errata/RHSA-2026:52978
- access.redhat.com/errata/RHSA-2026:54532
- access.redhat.com/errata/RHSA-2026:59277
- access.redhat.com/errata/RHSA-2026:59278
- access.redhat.com/errata/RHSA-2026:66488
- access.redhat.com/errata/RHSA-2026:66545
- access.redhat.com/security/cve/CVE-2026-42198
- bugzilla.redhat.com/show_bug.cgi?id=2463857
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42198.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.