CVE-2026-16240

published 12 Nov 2026 · updated 14 Nov 2026

PostgreSQL pg_basebackup can use backup manifest content as a format string

3.7LowCVSS 3.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 14.25, 15.20, 16.16 and 2 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
<14.25, >=15 <15.20, >=16 <16.16, >=17 <17.12, >=18 <18.714.25, 15.20, 16.16, 17.12, 18.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-16240 severity on Zeptric[![CVE-2026-16240](https://zeptric.io/badge/cve/CVE-2026-16240.svg)](https://zeptric.io/cve/CVE-2026-16240)