Is CVE-2026-2006 exploited in the wild?

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

How severe is CVE-2026-2006?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-2006?

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-2006 attacked?

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

Am I affected by CVE-2026-2006?

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-2006: PostgreSQL buffer overflow in multibyte character manipulation

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

PostgreSQL is a widely used database system for storing and managing organizational data. A security flaw in how the database handles certain text characters allows a database user to run malicious commands on the underlying server. If exploited, this could lead to a full system takeover, unauthorized data access, or disruption of database services.

Technologies: PostgreSQL. Vendors: PostgreSQL.

Quick answers

Is CVE-2026-2006 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-2006 being exploited in the wild.
How severe is CVE-2026-2006?: High severity, with a CVSS score of 8.8, published 12 February 2026.
Which products and versions are affected?: PostgreSQL Before 18.2, 17.8, 16.12, 15.16, 14.21.
Is there a fix for CVE-2026-2006?: 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-2006 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-2006?: 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 buffer overflow vulnerability exists in the PostgreSQL core server due to improper validation of multibyte character lengths during text manipulation. An authenticated database user can trigger this flaw by issuing specially crafted SQL queries. The root cause is identified as improper validation of array indices or input offsets (CWE-129/CWE-1285) when processing multibyte strings. Successful exploitation allows for a heap buffer overrun, enabling arbitrary code execution with the privileges of the operating system user running the PostgreSQL service. Patches are available in versions 18.2, 17.8, 16.12, 15.16, and 14.21.

Affected products

PostgreSQL PostgreSQL Before 18.2, 17.8, 16.12, 15.16, 14.21
Red Hat Red Hat Enterprise Linux 10 postgresql18, postgresql16

Timeline

2026-02-12: advisory: PostgreSQL released security advisory and fixed versions.
2026-02-12: patched
2026-05-19: patched: Red Hat released security updates for RHEL 10.

References

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