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

Published Nov 12, 2026
·
Updated

Type confusion from incomplete PostgreSQL type-cache invalidation allows an object creator to execute arbitrary code as the operating system user running the database, via a composite type change while its cache entry is being populated. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.

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 to a version that resolves this vulnerability.

    Fixed in 18.7

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

Which of the listed Alpine PostgreSQL packages are affected?

Only PostgreSQL 18 minor versions earlier than 18.7 are affected. PostgreSQL 15, 16, and 17 are unaffected because versions before PostgreSQL 18 are not affected.

2

What level of access does an attacker need?

The attacker needs privileges to create database objects. Exploitation involves changing a composite type while its type-cache entry is being populated.

3

What is the impact if exploitation succeeds?

An attacker can execute arbitrary code as the operating system user running the PostgreSQL database. This can affect confidentiality, integrity, and availability.

4

How can I determine whether my deployment is exposed?

Check whether the server is running PostgreSQL 18 and whether its minor version is earlier than 18.7. Deployments running PostgreSQL versions before 18 are not affected.

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