ALPINE-CVE-2026-116319: Use After Free
Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via reentrant returnnext() calls. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/postgresql15to a version that resolves this vulnerability.Fixed in 15.20-r0 - Upgrade
Upgrade
alpine/postgresql16to a version that resolves this vulnerability.Fixed in 16.16-r0 - Upgrade
Upgrade
alpine/postgresql17to a version that resolves this vulnerability.Fixed in 17.12-r0 - Upgrade
Upgrade
alpine/postgresql18to a version that resolves this vulnerability.Fixed in 18.7-r0 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 18.7 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 17.12 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 16.16 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 15.20 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 14.25
Event History
Frequently Asked Questions
What level of database access does an attacker need?
The attacker must be able to create the relevant object. Exploitation uses reentrant return_next() calls in PL/Perl and can result in arbitrary code execution as the operating system user running the database.
Which PostgreSQL release branches need updating?
PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The listed Alpine packages include postgresql15, postgresql16, postgresql17, and postgresql18.
What is the likely impact if exploitation succeeds?
Successful exploitation can execute arbitrary code with the privileges of the operating system account that runs PostgreSQL. The reported impact includes high confidentiality, integrity, and availability consequences.