UBUNTU-CVE-2026-16240: Low severity ubuntu/postgresql-9.3 vulnerability

Published Nov 13, 2026
·
Updated

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

8 affected components
ubuntu/postgresql-9.3*
ubuntu/postgresql-9.5*
ubuntu/postgresql-10*
ubuntu/postgresql-12*
ubuntu/postgresql-14*
ubuntu/postgresql-16*
ubuntu/postgresql-18*
ubuntu/postgresql-18*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 18.7
  2. Upgrade

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

    Fixed in 17.12
  3. Upgrade

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

    Fixed in 16.16
  4. Upgrade

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

    Fixed in 15.20
  5. Upgrade

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

    Fixed in 14.25

Event History

Nov 13, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

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