Skip to main content
Mallory
HighVulnerability

CVE-2026-2004: PostgreSQL intarray Selectivity Estimator Type-Validation RCE

Published Feb 12, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS8.8High · v3.1
EPSS1.3%71st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Postgresql
IdentifiersCVE-2026-2004CWE-843

CVE-2026-2004 is an input-type validation vulnerability in the PostgreSQL intarray extension's selectivity estimator function. Missing validation allows a database object creator to cause arbitrary code execution with the privileges of the operating system account running PostgreSQL. Affected releases include PostgreSQL 14 through 18 before versions 14.21, 15.16, 16.12, 17.8, and 18.2, respectively.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation crosses the database-to-operating-system privilege boundary, allowing an attacker with database object-creation privileges to execute arbitrary code as the PostgreSQL service account. This can compromise database confidentiality and integrity and disrupt availability, with access to other resources limited by the operating system permissions of that account. Root or administrator access is not inherently granted.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific workaround is documented. Until patched, restrict PostgreSQL network access to trusted clients to reduce exposure. Network restrictions do not prevent exploitation by an already authorized database object creator.

Remediation

Patch, then assume compromise.

Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, 14.21, or a later fixed release in the applicable branch, or install the distribution's corresponding security update. Debian bookworm fixes PostgreSQL 15 in 15.16-0+deb12u1; Debian trixie fixes PostgreSQL 17 in 17.8-0+deb13u1. For bundled deployments, apply the product vendor's security update: relevant fixes include Splunk Enterprise 10.4.0, 10.2.4, and 10.0.7; Tenable Security Center patches SC202607.1 or SC202607.2 as applicable; and ExtremeAnalytics, ExtremeCloud IQ - Site Engine, and ExtremeControl for Site Engine 26.02.11 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PostgresqlPostgresqlapplication
FAQ

Frequently asked questions

Is CVE-2026-2004 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-2004 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-2004?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-2004.
Is there a patch for CVE-2026-2004?
Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, 14.21, or a later fixed release in the applicable branch, or install the distribution's corresponding security update. Debian bookworm fixes PostgreSQL 15 in 15.16-0+deb12u1; Debian trixie fixes PostgreSQL 17 in 17.8-0+deb13u1.
What products are affected by CVE-2026-2004?
Postgresql.
How severe is CVE-2026-2004?
CVE-2026-2004 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.3% (71st percentile) as of Nov 7, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity12Community discussion across Reddit, Mastodon, and other social sources.