CVE-2026-2006: PostgreSQL missing validation of multibyte character length executes arbitrary code

Published Feb 12, 2026
·
Updated

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices 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.

Affected Software

10 affected components
PostgreSQL postgresql<18.2
PostgreSQL postgresql<17.8
PostgreSQL postgresql<16.12
PostgreSQL postgresql<15.16
PostgreSQL postgresql<14.21
PostgreSQL postgresql>=14.0<14.21
PostgreSQL postgresql>=15.0<15.16
PostgreSQL postgresql>=16.0<16.12
PostgreSQL postgresql>=17.0<17.8
PostgreSQL postgresql>=18.0<18.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.8
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.12
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.16
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 14.21

Event History

Feb 12, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·02:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-2006?

CVE-2026-2006 is considered a high-severity vulnerability due to the potential for arbitrary code execution.

2

How do I fix CVE-2026-2006?

To fix CVE-2026-2006, you should update PostgreSQL to the latest version where the vulnerability is patched.

3

What versions of PostgreSQL are affected by CVE-2026-2006?

CVE-2026-2006 affects PostgreSQL versions up to 18.2, 17.8, 16.12, 15.16, and 14.21.

4

What are the potential risks associated with CVE-2026-2006?

The potential risks of CVE-2026-2006 include unauthorized access and the ability to execute arbitrary code on the database server.

5

Who can exploit CVE-2026-2006?

CVE-2026-2006 can be exploited by any authenticated database user capable of issuing specially crafted queries.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203