CVE-2026-87027: TDE temporary-file encryption key incompletely initialized in EDB Postgres Extended Server and EDB Postgres Advanced Server
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
EDB Postgres Extended Serverto a version that resolves this vulnerability.Fixed in 15.20 - Upgrade
Upgrade
EDB Postgres Extended Serverto a version that resolves this vulnerability.Fixed in 16.16 - Upgrade
Upgrade
EDB Postgres Extended Serverto a version that resolves this vulnerability.Fixed in 17.12 - Upgrade
Upgrade
EDB Postgres Extended Serverto a version that resolves this vulnerability.Fixed in 18.7 - Upgrade
Upgrade
EDB Postgres Advanced Serverto a version that resolves this vulnerability.Fixed in 15.20.0 - Upgrade
Upgrade
EDB Postgres Advanced Serverto a version that resolves this vulnerability.Fixed in 16.16.0 - Upgrade
Upgrade
EDB Postgres Advanced Serverto a version that resolves this vulnerability.Fixed in 17.12.0 - Upgrade
Upgrade
EDB Postgres Advanced Serverto a version that resolves this vulnerability.Fixed in 18.7.0 - Operational
Restart the server after upgrading.
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Only deployments of the affected EDB server versions with Transparent Data Encryption enabled are exposed. Exploitation additionally requires local read access to the server temporary-file directory.
Are permanent database files or WAL data affected?
No. The issue affects the encryption key used for temporary files only; permanent data files and WAL are not affected.
When could vulnerable temporary files be available to an attacker?
Temporary files normally exist only while the server is running. They can persist after a crash, but are removed at the next server start.
What should be done to remediate the issue?
Upgrade to EDB Postgres Extended Server 15.20, 16.16, 17.12, or 18.7, or EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0, or 18.7.0. Restart the server after upgrading.