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

Published Nov 12, 2026
·
Updated

Integer wraparound in PostgreSQL generation memory contexts allows a database user to execute arbitrary code as the operating system user running the database, via freeing an allocation larger than 1 GB and causing its block to be reused for smaller chunks whose back-pointer offset cannot represent that position. Within major versions 16-18, minor versions before PostgreSQL 18.7, 17.12, and 16.16 are affected. Versions before PostgreSQL 16 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 to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.7
  6. Upgrade

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

    Fixed in 17.12
  7. Upgrade

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

    Fixed in 16.16

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 deployments are affected?

PostgreSQL 16 through 18 are affected when below 16.16, 17.12, or 18.7, respectively. PostgreSQL versions before 16 are unaffected; the listed Alpine package set includes postgresql16, postgresql17, and postgresql18, while postgresql15 corresponds to an unaffected major version.

2

What level of access does an attacker need?

An attacker needs database-user privileges. No user interaction is required, and successful exploitation can result in arbitrary code execution as the operating system account that runs PostgreSQL.

3

What is the recommended remediation?

Upgrade affected PostgreSQL installations to 16.16, 17.12, or 18.7 or later within the corresponding major version.

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