LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2004: PostgreSQL intarray missing validation of type of input to selectivity estimator executes arbitrary code

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can let a PostgreSQL database user with object-creation capability run arbitrary code as the operating system account that runs PostgreSQL. It is serious because database compromise can become server-level compromise. The sources do not show active exploitation or CISA KEV listing.

Executive priority

Treat this as a high-priority database maintenance item. Prioritize internet-facing, shared, or multi-tenant PostgreSQL environments, especially where application or analyst roles can create database objects.

Technical view

PostgreSQL's intarray extension lacks input type validation in a selectivity estimator function. An object creator can trigger arbitrary code execution under the PostgreSQL server OS user. Affected releases are before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21. CVSS is 8.8, network reachable, low privilege, no user interaction.

Likely exposure

Exposure is most likely where PostgreSQL uses the intarray extension and non-administrative roles can create database objects. This is not described as unauthenticated remote exploitation; the source states an object creator is required.

Exploitation context

The bundled sources rate this high and describe arbitrary code execution as the database OS user. KEV is false, and no provided source states active exploitation. Evidence is limited to vendor and CVE records in the bundle.

Researcher notes

The key condition is object creation capability plus presence of the intarray extension. The record names fixed upstream versions but does not provide exploit details, public exploitation evidence, or complete product packaging status for every distribution.

Mitigation direction

  • Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, or 14.21 or later.
  • Apply relevant vendor packages, including Red Hat errata where applicable.
  • Identify databases using the intarray extension and prioritize them for patching.
  • Review object-creation privileges and reduce unnecessary access where operationally possible.
  • Check managed database provider guidance for patch timing and service-specific actions.

Validation and detection

  • Inventory PostgreSQL server versions across production and non-production environments.
  • Confirm whether the intarray extension is installed in each database.
  • Review roles with object-creation permissions in databases using intarray.
  • Verify patched package versions after maintenance windows complete.
  • Track applicable Red Hat advisories if using Red Hat PostgreSQL packages.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1287: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2004 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
35Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9PostgreSQL
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-2004Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPpostgresql: PostgreSQL intarray missing validation of type of input to selectivity estimator executes arbitrary code
other:Red Hat severity ratingcvssV3_1
  • 2026-02-12T14:01:31.249Z: Reported to Red Hat.
  • 2026-02-12T13:00:08.857Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aPostgreSQL18, 17, 16, 15, 0unaffected
Weakness

CWE details

CWE-1287

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1287 · source CWE mapping

Improper Validation of Specified Type of Input

Improper Validation of Specified Type of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs