UBUNTU-CVE-2026-16240: Low severity ubuntu/postgresql-9.3 vulnerability
Use of externally-controlled format string in PostgreSQL pgbasebackup allows an attacker having already compromised a server to achieve disclosure from pgbasebackup memory, via backup manifest bytes. The vulnerability does not return the improperly-read bytes back to the attacker's server, so a successful attack would need separate implementation-specific secrets for that. Integrity impact is unlikely; in particular, the applicable formatter does not support %n. 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 to a fixed release to a version that resolves this vulnerability.
Fixed in 18.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.16 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.20 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.25
Event History
Frequently Asked Questions
Who can realistically exploit this issue?
An attacker must already have compromised a PostgreSQL server and be able to influence backup manifest bytes processed by pg_basebackup. It is not described as a path to compromise an otherwise secure server.
What versions contain the fix?
The issue is fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. Versions earlier than those releases are affected.
What is the practical impact of successful exploitation?
The issue can disclose data from pg_basebackup memory. The improperly read bytes are not returned to the attacker's server, so obtaining useful secrets additionally requires separate implementation-specific means to expose them; integrity impact is unlikely because the formatter does not support %n.