CVE-2026-16239: PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code

Published Aug 13, 2026
·
Updated

Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

Affected Software

1 affected component
PostgreSQL postgresql<14.24, <15.19, <16.15, <17.11, <18.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 18.5
  2. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.11
  3. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.15
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.19
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.24

Event History

Aug 13, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-16239?

CVE-2026-16239 has a severity score of 8.8, indicating a high risk.

2

How do I fix CVE-2026-16239?

To address CVE-2026-16239, upgrade to PostgreSQL versions 18.5, 17.11, 16.15, 15.19, or 14.24.

3

What types of systems are affected by CVE-2026-16239?

CVE-2026-16239 affects PostgreSQL systems prior to versions 18.5, 17.11, 16.15, 15.19, and 14.24.

4

What does CVE-2026-16239 allow an attacker to do?

CVE-2026-16239 allows an attacker to execute arbitrary code as the operating system user running the PostgreSQL database.

5

What causes CVE-2026-16239?

CVE-2026-16239 is caused by type confusion in the cursor lifecycle of PostgreSQL.

Company

Resources

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
CVE-2026-16239 - PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code - SecAlerts