{"affected":[{"defaultStatus":"unaffected","product":"PostgreSQL","source":"CNA: PostgreSQL","vendor":"n/a","versions":[{"lessThan":"18.7","status":"affected","version":"18","versionType":"rpm"},{"lessThan":"17.12","status":"affected","version":"17","versionType":"rpm"},{"lessThan":"16.16","status":"affected","version":"16","versionType":"rpm"},{"lessThan":"15.20","status":"affected","version":"15","versionType":"rpm"},{"lessThan":"14.25","status":"affected","version":"0","versionType":"rpm"}]}],"cveId":"CVE-2026-16240","cwes":["CWE-134"],"description":"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.","epss":null,"exploits":[],"kev":null,"metrics":[{"score":3.7,"severity":"low","source":"CNA: PostgreSQL","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"}],"modifiedAt":1794492931280,"publishedAt":1794492931280,"references":[{"source":"CNA: PostgreSQL","tags":[],"url":"https://www.postgresql.org/support/security/CVE-2026-16240/"}],"remediation":[],"revision":"67d1b9e3db6dfc8b50f3e91935f0d5d4b1c5c66c42d236ea11bd01b1d6da27c0","sources":[{"modifiedAt":1794492931280,"name":"CNA: PostgreSQL","retrievedAt":1794496325392,"url":"https://www.cve.org/CVERecord?id=CVE-2026-16240"}],"ssvc":null,"status":"published","title":"PostgreSQL pg_basebackup can use backup manifest content as a format string","updatedAt":1794496325392}