CVE-2026-87027 · Vendor
NO FIX YET · SEE WHAT TO DO
With Transparent Data Encryption enabled, EDB Postgres Extended and Advanced Server fill only 8 of 32 key bytes from a secure random source for temporary files. The remaining 24 bytes keep old memory contents, cutting key randomness from 256 to 64 bits.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only servers running EDB Postgres Extended or Advanced Server 15 to 18 with Transparent Data Encryption turned on are affected. The weakness is in temporary-file keys, which exist only while the server runs, so an attacker needs local read access to the server's temporary-file directory and must find files left after a crash. Permanent data files and WAL are not affected, and teams not using TDE or not running EDB builds can skip it.
Not affected if community-postgres, no-tde, permanent-data-only
Who cares edb-postgres, postgres, self-hosted, tde
SHOW server_version; and whether Transparent Data Encryption is enabled15.20, 16.16, 17.12, 18.715.20.0, , , In EDB Postgres Extended Server and EDB Postgres Advanced Server versions 15 through 18 with Transparent Data Encryption (TDE) enabled, the key used to encrypt temporary files was incompletely initialized. The code applied sizeof() to a pointer to the key buffer rather than to the buffer itself, so only 8 of the intended 32 bytes were filled from a secure random source and the remaining 24 bytes kept whatever was already in memory. This reduces the guaranteed randomness of the temporary-file key from 256 bits to 64 bits. Exploiting this requires local read access to the server's temporary-file directory, and those files normally exist only while the server is running; they persist only after a crash and are removed at the next server start. Permanent data files and WAL are not affected. The issue is fixed in EDB Postgres Extended Server 15.20, 16.16, 17.12 and 18.7 and EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0 and 18.7.0; the server must be restarted after upgrading.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
16.16.017.12.018.7.0