VulnerabilityPublished 29 Apr 2026Updated 4 Nov 2026

CVE-2026-42198: Libpgjava · pgjdbc is an open source postgresql JDBC Driver

Affects libpgjavaSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High · fixed in 42.7.11 : patch libpgjava soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 3.2% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 42.7.11

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10libpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=stonking`Other threats	Affected 42.7.10-1 – 42.7.13-1 4 affected builds	Fixed in–
Ubuntu 26.04 LTSlibpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=resolute`Other threats	Affected 42.7.7-1 – 42.7.10-1 5 affected builds	Fixed in–
Ubuntu 25.10libpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=questing`Other threats	Affected =42.7.5-1 =42.7.5-2 =42.7.7-1	Fixed in–
Ubuntu 24.04 LTSlibpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=noble`Other threats	Affected 42.5.4-1 – 42.7.2-1 5 affected builds	Fixed in–
Ubuntu 22.04 LTSlibpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=jammy`Other threats	Affected 42.2.23-1 – 42.3.3-1 5 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSlibpgjava`pkg:deb/ubuntu/libpgjava?arch=source&distro=esm-apps/focal`Other threats	Affected 42.2.6-1 – 42.2.10-1ubuntu0.1~esm1 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade pgjdbc to version 42.7.11 or later, where this vulnerability is fixed. The loginTimeout setting does not fully mitigate the issue, so patching is required to prevent CPU exhaustion during SCRAM-SHA-256 authentication.

Description

pgjdbc, the open source PostgreSQL JDBC driver, has a client-side denial of service vulnerability in versions from 42.2.0 up to but not including 42.7.11. A malicious server can cause the client to perform SCRAM-SHA-256 authentication with an excessively large iteration count, causing the client to consume unbounded CPU time during PBKDF2 computation. This can exhaust client CPU resources and block connection pools. The loginTimeout setting does not fully mitigate this issue as the worker thread continues CPU-intensive processing even after timeout. The vulnerability is fixed in version 42.7.11.

Impact

An attacker controlling a malicious PostgreSQL server can cause clients using vulnerable versions of pgjdbc to consume excessive CPU resources during authentication, resulting in denial of service. This can degrade client performance and exhaust connection pools, impacting availability. There is no impact on confidentiality or integrity. The vulnerability is rated high severity with a CVSS score of 7.5.

Summary

The vulnerability in pgjdbc affects versions 42.2.0 through before 42.7.11. It allows a malicious PostgreSQL server to trigger a client-side denial of service by specifying a very large iteration count during SCRAM-SHA-256 authentication. This forces the client to spend excessive CPU time in the PBKDF2 key derivation function, potentially tying up a CPU core indefinitely. The loginTimeout parameter does not fully prevent CPU exhaustion because the worker thread performing authentication continues running after the timeout expires. This flaw has been patched in version 42.7.11.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 21:37 UTC

Technical details

References

Community reviews

Related threats