dbcve.org
PostgreSQLDatabase / datastore

CVE-2026-2004

HIGH · 8.8 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 14.21 / 15.16 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A missing type validation vulnerability exists in the PostgreSQL intarray extension's selectivity estimator function. An attacker who can create database objects can craft malicious input that bypasses type checking, allowing arbitrary code execution with the privileges of the operating system user running the PostgreSQL server.

MitigationUpgrade PostgreSQL to version 18.2, 17.8, 16.12, 15.16, or 14.21 or later. If the intarray extension is not required, disable or drop it to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PostgreSQLDatabase / datastore
Affected:>= 14.0, < 14.21>= 15.0, < 15.16>= 16.0, < 16.12>= 17.0, < 17.8>= 18.0, < 18.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check PostgreSQL server version
    Run `SELECT version();` from psql or use `psql --version` from command line
    Affected if Version is 14.0 through 14.20, 15.0 through 15.15, 16.0 through 16.11, 17.0 through 17.7, or 18.0 through 18.1 (i.e., any version in the ranges >= 14.0 < 14.21, >= 15.0 < 15.16, >= 16.0 < 16.12, >= 17.0 < 17.8, >= 18.0 < 18.2)
  2. Confirm intarray extension is installed
    Run `SELECT * FROM pg_extension WHERE extname = 'intarray';` in the target database
    Affected if The intarray extension is present in the database (vulnerable code path requires the extension to be loaded)
  3. Check for users with object creation privileges
    Run `SELECT rolname FROM pg_roles WHERE rolcreatedb = true OR rolcanlogin = true;` and review database users
    Affected if Any database user has permission to create objects (the attack requires the attacker to be able to create database objects)

You are affected if your PostgreSQL version falls within the vulnerable ranges AND the intarray extension is installed in your database AND an untrusted user has permission to create database objects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.21 / 15.16 / 16.12 or later
Fixed in 14.2115.1616.12
Interim mitigation

Upgrade PostgreSQL to version 18.2, 17.8, 16.12, 15.16, or 14.21 or later. If the intarray extension is not required, disable or drop it to reduce attack surface.

Recommended fix High confidence

PostgreSQL 14.21, 15.16, 16.12, or 17.8 (upgrade within your current major version branch)

  1. Schedule a planned maintenance window for the database upgrade
  2. Create a full backup of all PostgreSQL databases before proceeding
  3. Identify your current PostgreSQL major version (14, 15, 16, or 17)
  4. Upgrade PostgreSQL to the corresponding fixed version: 14.21 for 14.x, 15.16 for 15.x, 16.12 for 16.x, or 17.8 for 17.x
  5. For package-based installations (Yum/DNF/Apt), run: sudo yum/dnf/apt update postgresqlXX where XX is your major version, or download and install from the official PostgreSQL repository
  6. For source installations, compile and install from PostgreSQL source version 14.21, 15.16, 16.12, or 17.8 as appropriate
  7. After upgrade, start/restart the PostgreSQL service
  8. Verify the intarray extension is functional and the server is accepting connections
Caveat Minor version upgrades within the same major version (e.g., 17.x to 17.8) are backward compatible and typically non-breaking; however, always test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in PostgreSQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2004 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data