BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-42198High confidence

pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS

pgjdbc · pgjdbc

Official source article: GitHub GHSA-98QH-XJC8-98PQ ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 4.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs pgjdbc pgjdbc and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelibpgjavaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelibpgjavaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelibpgjavaVendor fix publishedDebian records a fixed source-package version for this release.42.7.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelibpgjavaVendor fix publishedDebian records a fixed source-package version for this release.42.7.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelibpgjavaUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.postgresql:postgresqlECOSYSTEM: introduced 42.2.0; fixed 42.7.1142.7.11OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.postgresql:postgresql>= 42.2.0, < 42.7.1142.7.11GitHub advisory ↗upstream repository advisory · 5 May 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-42198 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjdbc.postgresql.org: pgjdbc: Client-side Denial of Service via malicious SCRAM-SHA-256 authentication
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • postgresql-jdbc as a component of Red Hat Enterprise Linux 6
  • postgresql-jdbc.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in pgjdbc, an open-source PostgreSQL JDBC Driver. A malicious server can exploit this vulnerability by instructing the driver to perform SCRAM-SHA-256 (Salted Challenge Response Authentication Mechanism Secure Hash Algorithm 256) authentication with an excessively large iteration count. This causes the client to spend an unbounded amount of CPU time performing PBKDF2 (Password-Based Key Derivation Function 2) computations, leading to a client-side Denial of Service (DoS). This can exhaust client CPU resources and wedge connection pools.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-26247

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-26247Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2923Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye, und Jira): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2437Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2460Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
BSI · German · WID-SEC-2026-1955Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
BSI · German · WID-SEC-2026-1608Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um einen Cross-Site Scripting Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1754PostgreSQL JDBC Driver: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in PostgreSQL JDBC Driver ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 May 2026, published on 6 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42036 Référence CVE CVE-2026-42037 https://www.cve.org/CVERecord?id=CVE-2026-42037 Référence CVE CVE-2026-42038 https://www.cve.org/CVERecord?id=CVE-2026-42038 Référence CVE CVE-2026-42039 https://www.cve.org/CVERecord?id=CVE-2026-42039 Référence CVE CVE-2026-42040 https://www.cve.org/CVERecord?id=CVE-2026-42040 Référence CVE CVE-2026-42041 https://www.cve.org/CVERecord?id=CVE-2026-42041 Référence CVE CVE-2026-42042 https://www.cve.org/CVERecord?id=CVE-2026-42042 Référence CVE CVE-2026-42043 https://www.cve.org/CVERecord?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-42264 https://www.cve.org/CVERecord?id=CVE-2026-42264 Référence CVE CVE-2026-42402 https://www.cve.org/CVERecord?id=CVE-2026-42402 Référence CVE CVE-2026-42403 https://www.cve.org/CVERecord?id=CVE-2026-42403 Référence CVE CVE-2026-42404 https://www.cve.org/CVERecord?id=CVE-2026-42404 Référence CVE CVE-2026-42440 https://www.cve.org/CVERecord?id=CVE-2026-42440 Référence CVE CVE-2026-42577 https://www.cve.org/CVERecord?id=CVE-2026-42577 Référence CVE CVE-2026-42578 https://www.cve.org/CVERecord?id=CVE-2026-42578 Référence CVE CVE-2026-42579 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42036 Référence CVE CVE-2026-42037 https://www.cve.org/CVERecord?id=CVE-2026-42037 Référence CVE CVE-2026-42038 https://www.cve.org/CVERecord?id=CVE-2026-42038 Référence CVE CVE-2026-42039 https://www.cve.org/CVERecord?id=CVE-2026-42039 Référence CVE CVE-2026-42040 https://www.cve.org/CVERecord?id=CVE-2026-42040 Référence CVE CVE-2026-42041 https://www.cve.org/CVERecord?id=CVE-2026-42041 Référence CVE CVE-2026-42042 https://www.cve.org/CVERecord?id=CVE-2026-42042 Référence CVE CVE-2026-42043 https://www.cve.org/CVERecord?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-42253 https://www.cve.org/CVERecord?id=CVE-2026-42253 Référence CVE CVE-2026-42402 https://www.cve.org/CVERecord?id=CVE-2026-42402 Référence CVE CVE-2026-42403 https://www.cve.org/CVERecord?id=CVE-2026-42403 Référence CVE CVE-2026-42404 https://www.cve.org/CVERecord?id=CVE-2026-42404 Référence CVE CVE-2026-42561 https://www.cve.org/CVERecord?id=CVE-2026-42561 Référence CVE CVE-2026-42588 https://www.cve.org/CVERecord?id=CVE-2026-42588 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0934Multiples vulnérabilités dans les produits Atlassian

d?id=CVE-2026-29146 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-42033 https://www.cve.org/CVERecord?id=CVE-2026-42033 Référence CVE CVE-2026-42035 https://www.cve.org/CVERecord?id=CVE-2026-42035 Référence CVE CVE-2026-42041 https://www.cve.org/CVERecord?id=CVE-2026-42041 Référence CVE CVE-2026-42043 https://www.cve.org/CVERecord?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-42264 https://www.cve.org/CVERecord?id=CVE-2026-42264 Référence CVE CVE-2026-42581 https://www.cve.org/CVERecord?id=CVE-2026-42581 Référence CVE CVE-2026-42583 https://www.cve.org/CVERecord?id=CVE-2026-42583 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CVE-2026-44487 Référence CVE CVE-2026-44488 https://www.cve.org/CVERecord?id=CVE-2026-44488 Référence CVE CVE-2026-44490 https://www.cve.org/CVERecord?id=CVE-2026-44490 Référence CVE CVE-2026-44492 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0698Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42036 Référence CVE CVE-2026-42037 https://www.cve.org/CVERecord?id=CVE-2026-42037 Référence CVE CVE-2026-42038 https://www.cve.org/CVERecord?id=CVE-2026-42038 Référence CVE CVE-2026-42039 https://www.cve.org/CVERecord?id=CVE-2026-42039 Référence CVE CVE-2026-42040 https://www.cve.org/CVERecord?id=CVE-2026-42040 Référence CVE CVE-2026-42041 https://www.cve.org/CVERecord?id=CVE-2026-42041 Référence CVE CVE-2026-42042 https://www.cve.org/CVERecord?id=CVE-2026-42042 Référence CVE CVE-2026-42043 https://www.cve.org/CVERecord?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-44431 https://www.cve.org/CVERecord?id=CVE-2026-44431 Référence CVE CVE-2026-44432 https://www.cve.org/CVERecord?id=CVE-2026-44432 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-4923 https://www.cve.org/CVERecord?id=CVE-2026-4923 Référence CVE CVE-2026-4926 https://www.cve.org/CVERecord?id=CVE-2026-4926 Référence CVE CVE-2026-8620 https://www.cve.org/CVERecord?id=CVE-2026-8620 Référence CVE CVE-2026-8633 https://www.cve.org/CVERecord?id=CVE-2026-8633 Référence CVE CVE-2026-8644 https://www.cve.org/CVERecord?id=CVE-2026-86

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014210PostgreSQL.orgのPostgreSQL JDBC ドライバにおける制限またはスロットリング無しのリソースの割り当てに関する脆弱性

pgjdbcはオープンソースのPostgreSQL JDBCドライバーです。バージョン42.2.0から42.7.11未満のバージョンにおいて、SCRAM-SHA-256認証中にクライアント側でサービス拒否の脆弱性が存在します。悪意のあるサーバーは、ドライバーに対して非常に大きな反復回数でSCRAM認証を実行するよう指示できます。十分に大きな値を指定すると、認証が失敗する前にクライアントはPBKDF2内で無制限のCPU時間を消費します。単一の試行でもCPUコアを占有します。繰り返しまたは同時に試行すると、クライアントのCPUを枯渇させて接続プールを動作不能にする可能性があります。影響を受けるバージョンでは、loginTimeoutはこの問題を完全には軽減できません。loginTimeoutの期限が切れた場合、呼び出し元は待機を停止できますが、接続試行を行うワーカースレッドはSCRAM PBKDF2計算内で引き続きCPUを消費します。この問題はバージョン42.7.11で修正されました。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0325Kwetsbaarheden verholpen in Atlassian producten

pgjdbc versions 42.2.0 to before 42.7.11 are vulnerable to client-side denial of service via excessive CPU usage during SCRAM-SHA-256 authentication, fixed in 42.7.11, while Oracle Communications Cloud Native Core Console versions 25.1.203 and 25.2.201 have a network-accessible SQL injection denial of service vulnerability.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles4 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 29 Apr 2026 · Last source change 11 Sept 2026, 12:09 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-26247
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59277; removed vendor advisory: access.redhat.com/RHSA-2026:59278; 2 further removals.
    Before
    vendor advisory: access.redhat.com/RHSA-2026:59277 · vendor advisory: access.redhat.com/RHSA-2026:59278 · vendor advisory: access.redhat.com/RHSA-2026:66488 · 2 more references
    After
    vendor advisory: github.com/GHSA-98qh-xjc8-98pq
    security-advisories@github.com ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59277; added vendor advisory: access.redhat.com/RHSA-2026:59278; 2 further additions.
    Before
    vendor advisory: github.com/GHSA-98qh-xjc8-98pq
    After
    vendor advisory: access.redhat.com/RHSA-2026:59277 · vendor advisory: access.redhat.com/RHSA-2026:59278 · vendor advisory: access.redhat.com/RHSA-2026:66488 · 2 more references
    security-advisories@github.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    postgresql as a component of Red Hat AMQ Broker 7; postgresql-jdbc as a component of Red Hat Enterprise Linux 6; postgresql-jdbc.src as a component of Red Hat Enterprise Linux 6 · Fixed: postgresql-jdbc-0:42.7.1-7.el10_0.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.1-7.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.2-1.el10_2.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.7.2-1.el10_2.2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.14-4.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-javadoc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.28-1.el9_2.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_4.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_4.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); and 4 more
    After
    postgresql-jdbc as a component of Red Hat Enterprise Linux 6; postgresql-jdbc.src as a component of Red Hat Enterprise Linux 6 · Fixed: postgresql-jdbc-0:42.7.1-7.el10_0.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.1-7.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.2-1.el10_2.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.7.2-1.el10_2.2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.14-4.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-javadoc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.28-1.el9_2.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_4.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_4.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); and 6 more
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    postgresql as a component of Red Hat AMQ Broker 7; postgresql-jdbc as a component of Red Hat Enterprise Linux 6; postgresql-jdbc.src as a component of Red Hat Enterprise Linux 6 · Fixed: postgresql-jdbc-0:42.7.1-7.el10_0.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.1-7.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.2-1.el10_2.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.7.2-1.el10_2.2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.14-4.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-javadoc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.28-1.el9_2.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_4.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_4.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); postgresql-jdbc-0:42.2.28-1.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); postgresql-jdbc-0:42.2.28-2.el9_8.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9); postgresql-jdbc-0:42.2.28-2.el9_8.2.src as a component of Red Hat Enterprise Linux AppStream (v. 9); Red Hat build of Quarkus 3.27.3.SP2
    After
    postgresql as a component of Red Hat AMQ Broker 7; postgresql-jdbc as a component of Red Hat Enterprise Linux 6; postgresql-jdbc.src as a component of Red Hat Enterprise Linux 6 · Fixed: postgresql-jdbc-0:42.7.1-7.el10_0.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.1-7.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); postgresql-jdbc-0:42.7.2-1.el10_2.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.7.2-1.el10_2.2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); postgresql-jdbc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.14-4.el8_10.src as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-javadoc-0:42.2.14-4.el8_10.noarch as a component of Red Hat Enterprise Linux AppStream (v. 8); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-7.el8_4.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-javadoc-0:42.2.3-7.el8_4.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.4); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream AUS (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.3-5.el8_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-javadoc-0:42.2.3-5.el8_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.14-5.el8_8.1.src as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-javadoc-0:42.2.14-5.el8_8.1.noarch as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8); postgresql-jdbc-0:42.2.28-1.el9_2.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); postgresql-jdbc-0:42.2.28-1.el9_4.1.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_4.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); postgresql-jdbc-0:42.2.28-1.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); and 4 more
    Red Hat Product Security ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: added remediation: github.com/GHSA-98qh-xjc8-98pq.
    Before
    vendor advisory: github.com/GHSA-98qh-xjc8-98pq
    After
    remediation: github.com/GHSA-98qh-xjc8-98pq · vendor advisory: github.com/GHSA-98qh-xjc8-98pq
    security-advisories@github.com ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 42.2.0, < 42.7.11 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    pgjdbc: >= 42.2.0, < 42.7.11 · Fixed: RHSA-2026:52928: Red Hat Enterprise Linux AppStream EUS (v. 10.0)
    CNA ↗
  7. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    security-advisories@github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-42198 · cve.blacktree.nl