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

CVE-2026-2004 is a high-impact PostgreSQL issue in the intarray extension. A database user who can create objects could make PostgreSQL run arbitrary code as the operating system account running the database. This can threaten confidentiality, integrity, and availability of affected database hosts.

Executive priority

Treat this as a priority database platform update, especially for shared, internet-reachable, or user-extensible PostgreSQL environments. There is no provided evidence of active exploitation, but the impact includes full compromise of data and database host availability under the database OS account.

Technical view

The issue is missing input type validation in the PostgreSQL intarray extension selectivity estimator. The published CVSS is 8.8 with network access, low attack complexity, low privileges, no user interaction, and high CIA impact. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

Likely exposure

Exposure is most relevant where PostgreSQL uses the intarray extension and low-privileged database users can create objects. The bundle lists PostgreSQL 18, 17, 16, 15, and an unclear “0” entry, with fixed upstream versions named.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The issue is still serious because exploitation requires only low privileges, no user interaction, and can execute code as the database operating system user.

Researcher notes

Key uncertainty is deployment-specific exposure: the bundle ties the bug to intarray and object creation, but does not provide exploit telemetry or detailed product matrix beyond upstream and Red Hat references. Validate installed extensions, database role privileges, and package provenance before declaring systems exposed.

Mitigation direction

  • Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, 14.21, or later.
  • Apply relevant Red Hat advisories if using Red Hat packaged PostgreSQL.
  • Inventory databases using the intarray extension.
  • Review vendor guidance before applying temporary configuration workarounds.
  • Prioritize externally reachable or multi-tenant database environments.

Validation and detection

  • Check each PostgreSQL server version against the fixed-version list.
  • Confirm whether the intarray extension is installed in each database.
  • Review which roles can create objects in affected databases.
  • Verify OS vendor package advisories are applied where applicable.
  • Document any exposed systems awaiting vendor-approved remediation.
Prepared
Confidence
medium
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