ALPINE-CVE-2026-116306: High severity alpine/postgresql15 vulnerability

Published Nov 12, 2026
·
Updated

Type confusion in PostgreSQL composite-value field assignment allows an object creator to execute arbitrary code as the operating system user running the database, via changing a composite type between deforming and reforming a value. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Affected Software

12 affected componentsFixes available
alpine/postgresql15<15.20-r0
15.20-r0
alpine/postgresql15<15.20-r0
15.20-r0
alpine/postgresql16<16.16-r0
16.16-r0
alpine/postgresql16<16.16-r0
16.16-r0
alpine/postgresql16<16.16-r0
16.16-r0
alpine/postgresql16<16.16-r0
16.16-r0
alpine/postgresql17<17.12-r0
17.12-r0
alpine/postgresql17<17.12-r0
17.12-r0
alpine/postgresql17<17.12-r0
17.12-r0
alpine/postgresql17<17.12-r0
17.12-r0
alpine/postgresql18<18.7-r0
18.7-r0
alpine/postgresql18<18.7-r0
18.7-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/postgresql15 to a version that resolves this vulnerability.

    Fixed in 15.20-r0
  2. Upgrade

    Upgrade alpine/postgresql16 to a version that resolves this vulnerability.

    Fixed in 16.16-r0
  3. Upgrade

    Upgrade alpine/postgresql17 to a version that resolves this vulnerability.

    Fixed in 17.12-r0
  4. Upgrade

    Upgrade alpine/postgresql18 to a version that resolves this vulnerability.

    Fixed in 18.7-r0
  5. Upgrade

    Upgrade postgresql/postgresql to a version that resolves this vulnerability.

    Fixed in 18.7
  6. Upgrade

    Upgrade postgresql/postgresql to a version that resolves this vulnerability.

    Fixed in 17.12
  7. Upgrade

    Upgrade postgresql/postgresql to a version that resolves this vulnerability.

    Fixed in 16.16
  8. Upgrade

    Upgrade postgresql/postgresql to a version that resolves this vulnerability.

    Fixed in 15.20
  9. Upgrade

    Upgrade postgresql/postgresql to a version that resolves this vulnerability.

    Fixed in 14.25

Event History

Nov 12, 2026
CVE Published
via OSV·03:17 PM
Data Sourced
via OSV·03:17 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What level of access does an attacker need?

An attacker needs privileges to create an object in PostgreSQL. No user interaction is required, and the issue can be exploited remotely where the attacker can connect to the database.

2

What is the impact of successful exploitation?

Successful exploitation allows arbitrary code execution as the operating system user running the PostgreSQL database. This can compromise the confidentiality, integrity, and availability of resources accessible to that OS account.

3

Which PostgreSQL versions contain the fix?

The issue is fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. Earlier versions in those release branches are affected.

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