CVE-2026-87027
Last modified
CVE-2026-87027 is a medium-severity vulnerability rated 5.6/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| EnterpriseDB | EDB Postgres Extended Server | >= 15.0, < 15.20; >= 16.0, < 16.16; >= 17.0, < 17.12; >= 18.0, < 18.7 |
| EnterpriseDB | EDB Postgres Advanced Server | >= 15.0, < 15.20.0; >= 16.0, < 16.16.0; >= 17.0, < 17.12.0; >= 18.0, < 18.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-87027?
How severe is CVE-2026-87027?
How do I fix CVE-2026-87027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-87021Tanium addressed an unauthorized code execution vulnerabilit…7.2
- CVE-2026-87022Improper handling of length parameter inconsistency vulnerab…7.5
- CVE-2026-87023Tanium addressed a path traversal vulnerability in Comply.8.5
- CVE-2026-87024Tanium addressed a SQL injection vulnerability in Asset.7.2
- CVE-2026-87025Tanium addressed an improper access controls vulnerability i…5.4
- CVE-2026-87026Tanium addressed an improper access controls vulnerability i…3.8
- CVE-2026-87028Concrete CMS 9 through 9.5.3 did not confirm that a board In…6.5
- CVE-2026-87029undici is an HTTP client library for Node.js. In versions 7.…7.5
- CVE-2026-8703The Endless Scroll plugin for WordPress is vulnerable to Sto…6.4
- CVE-2026-87030Tanium addressed a path traversal vulnerability in Comply.8.5
- CVE-2026-87031n Concrete CMS 9.2.0 through 9.5.3, the REST API user creati…2.7
- CVE-2026-87032Tanium addressed an information disclosure vulnerability in …4.3
Are you affected by CVE-2026-87027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
