CVE-2026-16240 PUBLISHED

PostgreSQL pg_basebackup can use backup manifest content as a format string

Assigner: PostgreSQL
Reserved: 20.07.2026 Published: 12.11.2026 Updated: 12.11.2026

Use of externally-controlled format string in PostgreSQL pg_basebackup allows an attacker having already compromised a server to achieve disclosure from pg_basebackup 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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS Score: 3.7

Product Status

Vendor n/a
Product PostgreSQL
Versions Default: unaffected
  • affected from 18 to 18.7 (excl.)
  • affected from 17 to 17.12 (excl.)
  • affected from 16 to 16.16 (excl.)
  • affected from 15 to 15.20 (excl.)
  • affected from 0 to 14.25 (excl.)

Affected Configurations

attacker has compromised the server being backed up; attacker has a separate way to retrieve the improperly-read bytes from the host running pg_basebackup; victim runs a backup without starting the server from that backup

Credits

  • The PostgreSQL project thanks Peter Eisentraut for reporting this problem.

References

Problem Types

  • Use of Externally-Controlled Format String CWE