PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-42198 pgjdbc CVE debrief

A vulnerability in pgjdbc, a PostgreSQL JDBC driver, can cause a client-side denial of service during SCRAM-SHA-256 authentication. A malicious server can instruct the driver to perform SCRAM authentication with a large iteration count, leading to high CPU usage and potential exhaustion of client CPU resources. This issue affects versions 42.2.0 to before 42.7.11 of pgjdbc. Defenders should assess exposure and prioritize patching to prevent potential denial of service attacks. The vulnerability can be mitigated by upgrading to version 42.7.11 or later and verifying loginTimeout settings.

Vendor
pgjdbc
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-29
Original CVE updated
2026-09-11
Advisory published
2026-04-29
Advisory updated
2026-09-11

Who should care

Defenders responsible for PostgreSQL databases using the pgjdbc driver, specifically those using versions 42.2.0 to before 42.7.11, should assess exposure and prioritize patching to prevent potential denial of service attacks.

Why it matters

CVE-2026-42198 is a client-side denial of service vulnerability in pgjdbc during SCRAM-SHA-256 authentication. Defenders should prioritize patching, assess exposure, and verify configurations to prevent potential attacks.

  • Denial of service due to high CPU usage
  • Potential exhaustion of client CPU resources
  • Need for patching vulnerable versions
  • Verification of loginTimeout settings

Technical summary

The pgjdbc vulnerability causes a client-side denial of service during SCRAM-SHA-256 authentication due to a large iteration count. This can lead to high CPU usage and potential exhaustion of client CPU resources. The vulnerability affects versions 42.2.0 to before 42.7.11 of pgjdbc. The issue can be mitigated by upgrading to version 42.7.11 or later and verifying loginTimeout settings to prevent potential attacks. The vulnerability is a result of the driver's implementation of the SCRAM-SHA-256 authentication mechanism, which allows a malicious server to instruct the driver to perform SCRAM authentication with a large iteration count.

Defensive priority

Defenders should prioritize patching vulnerable versions of pgjdbc, specifically upgrading to version 42.7.11 or later, and assess exposure in their environments.

Recommended defensive actions

  • Patch vulnerable versions of pgjdbc by upgrading to version 42.7.11 or later
  • Assess exposure in environments using affected versions of pgjdbc
  • Monitor for potential denial of service attacks
  • Verify loginTimeout settings to ensure they are properly configured
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, while the vendor advisory and release notes offer guidance on patching and mitigation. The vulnerability was patched in version 42.7.11 of pgjdbc. Defenders should verify configurations and assess exposure in their environments. The issue has been publicly disclosed and patched, with no indication of exploitation in the wild. The CVE record and NVD entry provide additional context on the vulnerability and its impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-42198 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-42198

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-42198 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-42198

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/pgjdbc/pgjdbc/releases/tag/REL42.7.11

    [email protected] - Release Notes

  • Source reference

    Unverified legacy reference

    URL: https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-98qh-xjc8-98pq

    [email protected] - Vendor Advisory

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:19098

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

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

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:24348

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:25030

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:52928

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

  • Source reference

    Unverified legacy reference

    URL: https://access.redhat.com/errata/RHSA-2026:52929

    0b0ca135-0b70-47e7-9f44-1890c2a1c46c

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.