Cyber Resilience

CVE-2026-2006

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.011 62th percentile
Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2026-2006 is a high-severity Improper Validation of Array Index (CWE-129) 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 38% 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-2006 is a vulnerability in PostgreSQL's text manipulation functions stemming from missing validation of multibyte character length, which enables a buffer overrun (CWE-129). It affects versions prior to PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21. The issue was published on 2026-02-12 and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

A database user with low privileges (PR:L) can exploit this vulnerability remotely over the network (AV:N) with low attack complexity (AC:L) and without requiring user interaction (UI:N). By issuing crafted queries, the attacker triggers the buffer overrun, achieving arbitrary code execution with the privileges of the operating system user running the PostgreSQL database process.

The official PostgreSQL security advisory at https://www.postgresql.org/support/security/CVE-2026-2006/ details mitigation steps, which include upgrading to one of the fixed versions: 18.2, 17.8, 16.12, 15.16, or 14.21.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL…

more

18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

CWE(s)
CWE-129CWE-1285

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 →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
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-6637Same product: Postgresql Postgresql
CVE-2026-2005Same product: Postgresql Postgresql
CVE-2026-2003Same product: Postgresql Postgresql
CVE-2026-2004Same product: Postgresql Postgresql
CVE-2026-2007Same product: Postgresql Postgresql
CVE-2026-6477Same product: Postgresql Postgresql
CVE-2026-6473Same product: Postgresql Postgresql
CVE-2026-6474Same product: Postgresql Postgresql
CVE-2026-6472Same product: Postgresql Postgresql
CVE-2024-4317Same 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.4.2
  • V2.1.1
  • V2.2.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.

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 input validation and bounds checking that prevent improper array indexing.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
prevents

Patching and replacement can remediate instances of the weakness after discovery.

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 in development can detect out-of-bounds array access but does not prevent the weakness by itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

A.8.26 Application security requirements partial match
prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

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

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

References