CVE-2026-2004 Vulnerability Analysis & Exploit Details

CVE-2026-2004
Vulnerability Scoring

8.8

/10

Severe Risk

Cybersecurity professionals consider CVE-2026-2004 an immediate threat requiring urgent mitigation.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2026-2004 Details

Status: Analyzed

Last updated: 🕢 20 Feb 2026, 19:53 UTC
Originally published on: 🕑 12 Feb 2026, 14:16 UTC

Time between publication and last update: 8 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-2004 Vulnerability Summary

CVE-2026-2004: Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

Assessing the Risk of CVE-2026-2004

Access Complexity Graph

The exploitability of CVE-2026-2004 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-2004

CVE-2026-2004 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-2004, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-2004, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2026-2004 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2026-2004 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: High
CVE-2026-2004 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-2004 References

External References

https://www.postgresql.org/support/security/CVE-2026-2004/

CWE Common Weakness Enumeration

CWE-1287

Vulnerable Configurations

cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.19:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.19:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.20:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.20:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-2004: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2026-29127 – The IDC SFX2100 Satellite Receiver sets overly permissive file system permissions on the monitor user's home directory. The directory is configured...
CVE-2026-26034 – UPS Multi-UPS Management Console (MUMC) version 01.06.0001 (A03) contains an Incorrect Default Permissions (CWE-276) vulnerability that allows an a...
CVE-2026-26033 – UPS Multi-UPS Management Console (MUMC) version 01.06.0001 (A03) contains an Unquoted Search Path or Element (CWE-428) vulnerability, which allows ...
CVE-2024-57854 – Net::NSCA::Client versions through 0.009002 for Perl uses a poor random number generator. Version v0.003 switched to use Data::Rand::Obscure inste...
CVE-2026-3381 – Compress::Raw::Zlib versions through 2.219 for Perl use potentially insecure versions of zlib. Compress::Raw::Zlib includes a copy of the zlib lib...