CVE-2026-116304: PostgreSQL parallel RECORD typmod use-after-free executes arbitrary code

Published Nov 12, 2026
·
Updated

Use after free in PostgreSQL coordination of anonymous RECORD type identifiers among parallel workers allows a database user to execute arbitrary code as the operating system user running the database, via causing one process to free a shared tuple descriptor while another process retains and later uses its address. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Affected Software

6 affected components
debian/postgresql-15*
debian/postgresql-17*
debian/postgresql-18*
debian/postgresql-15<=15.18-0+deb12u1, <=15.19-0+deb12u1
debian/postgresql-17<=17.11-0+deb13u1
debian/postgresql-18<=18.6-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 18.7
  2. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.12
  3. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.16
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.20
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.25

Event History

Nov 12, 2026
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·06:47 PM
DescriptionAffected Software

Frequently Asked Questions

1

Who can exploit this vulnerability?

An attacker needs to be able to act as a database user. Successful exploitation can execute arbitrary code as the operating system account that runs PostgreSQL.

2

Which PostgreSQL releases contain the fix?

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later release in the corresponding supported branch.

3

Does exploitation require interaction from another user?

No. The severity vector indicates no user interaction is required, but the attacker must have low-level privileges.

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