ALPINE-CVE-2026-120152: Use After Free

Published Nov 12, 2026
·
Updated

Use after free in PostgreSQL pgshowallsettings() allows a database user to retrieve memory contents, via loading a module while the function is scanning custom-variable placeholders that the module replaces and frees. 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, 17, and 18 are affected when running versions earlier than 16.16, 17.12, or 18.7, respectively. PostgreSQL versions before 16 are unaffected; this includes the listed alpine/postgresql15 package.

2

What access does an attacker need?

An attacker must already be a database user with privileges sufficient to load a module. Exploitation occurs while pg_show_all_settings() scans custom-variable placeholders that a loaded module replaces and frees.

3

What is the impact of successful exploitation?

Successful exploitation can disclose memory contents to the database user. The provided severity vector indicates no integrity or availability impact.

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