Postgresql Jdbc DriverDatabase / datastore · PostgreSQL
CVE-2026-42198
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpgjdbc 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepgjdbc versions 42.2.0 through 42.7.10 contain a client-side DoS vulnerability in SCRAM-SHA-256 authentication. A malicious server can specify an extremely large iteration count for PBKDF2, causing unbounded CPU consumption on the client. The loginTimeout setting does not fully mitigate this as the worker thread continues PBKDF2 computation after the timeout expires, allowing a single attack attempt to tie up a CPU core indefinitely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Postgresql Jdbc DriverDatabase / datastore
>= 42.2.0, < 42.7.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify pgjdbc driver versionLocate the pgjdbc JAR file in your classpath, application lib folder, or dependency management file (Maven pom.xml, Gradle build.gradle). The JAR filename follows the pattern pgjdbc-VERSION.jar. Alternatively, inspect the JAR manifest or programmatically call Driver.getVersion().Affected if Version is 42.2.0 through 42.7.10 inclusive (< 42.7.11)
-
Confirm SCRAM-SHA-256 authentication is enabledCheck your PostgreSQL server configuration (pg_hba.conf) for the authentication method set for your connections. Look for 'scram-sha-256' in the method column. Also verify your PostgreSQL server version is 10 or higher, which defaults to SCRAM-SHA-256.Affected if Connections use SCRAM-SHA-256 authentication (this is the default for PostgreSQL 10+)
You are affected if you have pgjdbc version 42.2.0 through 42.7.10 AND your PostgreSQL connections use SCRAM-SHA-256 authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped42.7.11
Upgrade pgjdbc to version 42.7.11 or later. Consider implementing connection timeout monitoring at the application level as a defense-in-depth measure until the upgrade is deployed.
42.7.11
- Upgrade the PostgreSQL JDBC Driver (pgjdbc) to version 42.7.11 or later
- If using Maven, update the dependency version in pom.xml from the current affected version to 42.7.11
- If using Gradle, update the dependency version in build.gradle or build.gradle.kts
- Rebuild and redeploy the application to incorporate the fixed driver
- Verify the upgrade by checking that the pgjdbc version in the classpath is 42.7.11 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Postgresql Jdbc Driver
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42198 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data