Cyber Resilience

CVE-2026-2004

Postgresql 14.0 – 14.21

Published
12 February 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 65th percentile
Risk Priority 66 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-2004 is a high-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Postgresql Postgresql. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 35% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-2004 stems from missing validation of input types in the selectivity estimator function of PostgreSQL's intarray extension. This vulnerability affects PostgreSQL versions prior to 18.2, 17.8, 16.12, 15.16, and 14.21. It allows an object creator to execute arbitrary code with the privileges of the operating system user running the database, as classified under CWE-1287.

The attack requires low privileges (PR:L), such as the ability to create database objects, and can be carried out remotely over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N). Exploitation yields high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), enabling arbitrary code execution as the database process's OS user, with a CVSS v3.1 base score of 8.8.

The official PostgreSQL security advisory at https://www.postgresql.org/support/security/CVE-2026-2004/ recommends upgrading to one of the patched versions—18.2, 17.8, 16.12, 15.16, or 14.21—which incorporate input type validation to prevent the arbitrary code execution.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-1287

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-2003Same product: Postgresql Postgresql
CVE-2026-14676Same product: Postgresql Postgresql
CVE-2026-2007Same product: Postgresql Postgresql
CVE-2026-14668Same product: Postgresql Postgresql
CVE-2026-14680Same product: Postgresql Postgresql
CVE-2026-19385Same product: Postgresql Postgresql
CVE-2026-14670Same product: Postgresql Postgresql
CVE-2026-16238Same product: Postgresql Postgresql
CVE-2026-14671Same product: Postgresql Postgresql
CVE-2026-14669Same product: Postgresql Postgresql

Affected Assets

postgresql
postgresql
14.0 — 14.21 · 15.0 — 15.16 · 16.0 — 16.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-validation flaws but does not prevent them during development.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly include validation of input data types and formats.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper type validation of all external inputs.

References