Technical impact
The vulnerability arises because the key used to encrypt temporary files in EnterpriseDB Postgres Extended Server and Advanced Server is only partially initialized. Instead of writing the full 32 bytes of random data, the code fills only the first 8 bytes, leaving the remaining 24 bytes unchanged and potentially containing predictable values. This reduces the effective key strength from 256 bits to 64 bits, making the encrypted temporary files substantially easier to reconstruct if an adversary can read them. The impact is thus a compromise of confidentiality for files written to the temporary directory while the server is running, but no effect on permanent data files or the WAL.
Affected Systems
Vulnerable versions include EnterpriseDB EDB Postgres Extended Server and Advanced Server 15, 16, 17, and 18 when Transparent Data Encryption is enabled. The flaw is fixed in Extended Server 15.20, 16.16, 17.12, and 18.7 as well as Advanced Server 15.20.0, 16.16.0, 17.12.0, and 18.7.0. Users of any earlier releases with TDE enabled are affected.
Risk and Exploitability
The CVSS base score of 5.6 indicates moderate severity. Exploitation requires local read access to the database's temporary-file directory, a condition that is typically limited to local system users or processes. The EPSS score is not available, and the vulnerability is not listed in CISA's KEV catalog. Given that temporary files are only created while the server is running and are deleted on reboot, the attack window is limited. Nonetheless, the weakened key randomness creates a clear opportunity for a local adversary to decode temporary files if they can read the directory.