Is CVE-2026-2004 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-2004 being exploited in the wild.

How severe is CVE-2026-2004?

High severity, with a CVSS score of 8.8, published 12 February 2026.

Which products and versions are affected?

PostgreSQL < 18.2, < 17.8, < 16.12, < 15.16, < 14.21.

Is there a fix for CVE-2026-2004?

A patch was published on 2026-02-12. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-2004 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-2004?

Check whether you run PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-2004: PostgreSQL intarray remote code execution in selectivity estimator

Q: Which products and versions are affected?

PostgreSQL < 18.2, < 17.8, < 16.12, < 15.16, < 14.21.

Q: Is there a fix for CVE-2026-2004?

A patch was published on 2026-02-12. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-2004 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-2004?

Check whether you run PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-2004 · Severity: high · CVSS 8.8 · Published 2026-02-12

A vulnerability exists in the 'intarray' extension of the PostgreSQL database, which is used for managing arrays of integers. An attacker with the ability to create database objects can exploit this flaw to execute unauthorized code on the server hosting the database. This could lead to a full system compromise, data theft, or service disruption, as the attacker would gain the same permissions as the database service itself.

Technologies: PostgreSQL. Vendors: PostgreSQL.

Quick answers

Is CVE-2026-2004 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-2004 being exploited in the wild.
How severe is CVE-2026-2004?: High severity, with a CVSS score of 8.8, published 12 February 2026.
Which products and versions are affected?: PostgreSQL < 18.2, < 17.8, < 16.12, < 15.16, < 14.21.
Is there a fix for CVE-2026-2004?: A patch was published on 2026-02-12. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-2004 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-2004?: Check whether you run PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability classified as Improper Validation of Specified Type of Input (CWE-1287) exists in the PostgreSQL 'intarray' contrib module. The root cause is a missing validation of input types within the selectivity estimator function. An attacker with 'object creator' permissions can leverage this lack of validation to trigger arbitrary code execution as the operating system user running the PostgreSQL service. The attack vector is over the network, requiring low-level authentication but no user interaction. Patches have been released in PostgreSQL versions 18.2, 17.8, 16.12, 15.16, and 14.21.

Affected products

PostgreSQL PostgreSQL < 18.2, < 17.8, < 16.12, < 15.16, < 14.21
Red Hat Red Hat Enterprise Linux 10

Timeline

2026-02-12: disclosed
2026-02-12: patched
2026-02-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.