Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-42198: pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS

HighCVSS 7.5 · v3.1—No exploit Fix available

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.

Published
Apr 29, 2026
Updated
Nov 11, 2026
EPSS
3.2% · 88th percentile

Report tools

JSON

Action score

31

Monitor

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.

Follow CVE-2026-42198

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
postgresqlpostgresql 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10postgresql-jdbcbefore 42.7.2-1.el10_2.242.7.2-1.el10_2.2
AlmaLinux:8postgresql-jdbcbefore 42.2.14-4.el8_1042.2.14-4.el8_10
AlmaLinux:8postgresql-jdbc-javadocbefore 42.2.14-4.el8_1042.2.14-4.el8_10
AlmaLinux:9postgresql-jdbcbefore 42.2.28-2.el9_8.242.2.28-2.el9_8.2
Debian:12libpgjavafrom 0—
Debian:14libpgjavabefore 42.7.11-142.7.11-1
Mavenorg.postgresql:postgresqlfrom 42.2.0 · before 42.7.1142.7.11
openSUSE:Tumbleweedpostgresql-jdbcbefore 42.7.11-1.142.7.11-1.1
Red Hat:enterprise_linux_eus:10.0postgresql-jdbcbefore 0:42.7.1-7.el10_0.10:42.7.1-7.el10_0.1
Red Hat:enterprise_linux:10.2postgresql-jdbcbefore 0:42.7.2-1.el10_2.20:42.7.2-1.el10_2.2
Red Hat:enterprise_linux:8::appstreampostgresql-jdbcbefore 0:42.2.14-4.el8_100:42.2.14-4.el8_10
Red Hat:enterprise_linux:8::appstreampostgresql-jdbc-javadocbefore 0:42.2.14-4.el8_100:42.2.14-4.el8_10
Red Hat:enterprise_linux:9::appstreampostgresql-jdbcbefore 0:42.2.28-2.el9_8.20:42.2.28-2.el9_8.2
Red Hat:rhel_aus:8.4::appstreampostgresql-jdbcbefore 0:42.2.3-7.el8_4.10:42.2.3-7.el8_4.1
Red Hat:rhel_aus:8.4::appstreampostgresql-jdbc-javadocbefore 0:42.2.3-7.el8_4.10:42.2.3-7.el8_4.1
Red Hat:rhel_aus:8.6::appstreampostgresql-jdbcbefore 0:42.2.3-5.el8_6.10:42.2.3-5.el8_6.1
Red Hat:rhel_aus:8.6::appstreampostgresql-jdbc-javadocbefore 0:42.2.3-5.el8_6.10:42.2.3-5.el8_6.1
Red Hat:rhel_e4s:8.8::appstreampostgresql-jdbcbefore 0:42.2.14-5.el8_8.10:42.2.14-5.el8_8.1
Red Hat:rhel_e4s:8.8::appstreampostgresql-jdbc-javadocbefore 0:42.2.14-5.el8_8.10:42.2.14-5.el8_8.1
Red Hat:rhel_e4s:9.2::appstreampostgresql-jdbcbefore 0:42.2.28-1.el9_2.10:42.2.28-1.el9_2.1
Red Hat:rhel_e4s:9.4::appstreampostgresql-jdbcbefore 0:42.2.28-1.el9_4.10:42.2.28-1.el9_4.1
Red Hat:rhel_eus:9.6::appstreampostgresql-jdbcbefore 0:42.2.28-1.el9_6.10:42.2.28-1.el9_6.1
Rocky Linux:10postgresql-jdbcbefore 0:42.7.2-1.el10_2.20:42.7.2-1.el10_2.2
Rocky Linux:8postgresql-jdbcbefore 0:42.2.14-4.el8_100:42.2.14-4.el8_10

+47

Other highest-scoring records for the same primary product.

  • CVE-2024-1597pgjdbc SQL Injection via line comment generation
    40Plan
  • 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 Classes
    40Plan

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 pgjdbc
    22Monitor
  • ← EarlierCVE-2025-49146Jun 11, 2025 · pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration
    23Monitor
  • Later →CVE-2026-54291Jul 6, 2026 · Silent channel-binding authentication downgrade via unsupported certificate algorithms
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
pgjdbc pgjdbc42.7.11 · descriptionVendor (CNA)
almalinux:postgresql-jdbc42.2.28-2.el9_8.2 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-jdbc-javadoc42.2.14-4.el8_10 · AlmaLinux:8Package registry (OSV)
debian:libpgjava42.7.11-1 · Debian:14Package registry (OSV)
Maven:org.postgresql:postgresql42.7.11Package registry (OSV)
opensuse:postgresql-jdbc42.7.11-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:postgresql-jdbc0:42.2.28-2.el9_8.2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:postgresql-jdbc-javadoc0:42.2.14-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:postgresql-jdbc0:42.2.28-2.el9_8.2 · Rocky Linux:9Package registry (OSV)
suse:postgresql-jdbc42.7.7-160000.3.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:suse-multi-linux-manager-5.1-aarch64-proxy-httpd-image5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-aarch64-proxy-salt-broker-image5.1.4-9.20.25 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-aarch64-proxy-squid-image5.1.4-8.20.11 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-aarch64-proxy-ssh-image5.1.4-8.20.12 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-aarch64-proxy-tftpd-image5.1.4-8.20.13 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-ppc64le-proxy-httpd-image5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-ppc64le-proxy-salt-broker-image5.1.4-9.20.25 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-ppc64le-proxy-squid-image5.1.4-8.20.11 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-ppc64le-proxy-ssh-image5.1.4-8.20.12 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-ppc64le-proxy-tftpd-image5.1.4-8.20.13 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package registry (OSV)
suse:suse-multi-linux-manager-5.1-s390x-proxy-httpd-image5.1.4-8.22.22 · SUSE:Multi-Linux Manager Proxy Extension for SLE 5.1Package 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.

EPSS, last 120 days

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

References

All records