Skip to main content
Menu
CVEs

CVE

EnterpriseDB EDB Postgres Extended Server weak randomness in TDE temporary-file encryption key

CVE-2026-87027

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

5.6MediumCNA
Exploited
No known exploitation
Fix
Fixed in EDB Postgres Extended Server 15.20, 16.16, 17.12, 18.7 · EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0, 18.7.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: EDB Postgres Extended Server 15.20, 16.16, 17.12, 18.7 · EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0, 18.7.0.

Published
Last modified
Reference
Last checked
6/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

EDB Postgres Extended Server and EDB Postgres Advanced Server, when Transparent Data Encryption is enabled, generate the key for encrypting temporary files with only 64 bits of real randomness instead of 256, because most of the key buffer is not filled from a secure random source. A local attacker who has high-privilege login and can read the server's temporary-file directory may be able to decrypt those temporary files, which exist only while the server runs or after a crash.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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.

cve.now Index

6Pcve.now Index 6 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.6/10CVSS 5.6
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: EDB Postgres Extended Server 15.20, 16.16, 17.12, 18.7 · EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0, 18.7.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-87027 (TDE temporary-file encryption key incompletely initialized in EDB Postgres Extended Server and EDB Postgres Advanced Server), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-87027 (entry last updated 2026-11-16):
Affected:
- EnterpriseDB EDB Postgres Extended Server: from 15.0, fixed in 15.20; from 16.0, fixed in 16.16; from 17.0, fixed in 17.12; from 18.0, fixed in 18.7
- EnterpriseDB EDB Postgres Advanced Server: from 15.0, fixed in 15.20.0; from 16.0, fixed in 16.16.0; from 17.0, fixed in 17.12.0; from 18.0, fixed in 18.7.0
Fixed versions: 15.20, 16.16, 17.12, 18.7, 15.20.0, 16.16.0, 17.12.0, 18.7.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-87027 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87027 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.enterprisedb.com/docs/security/advisories/cve202687027/
- https://www.enterprisedb.com/docs/pge/15/release_notes/rel_notes15.20/
- https://www.enterprisedb.com/docs/pge/16/release_notes/rel_notes16.16/
- https://www.enterprisedb.com/docs/pge/17/release_notes/rel_notes17.12/
- https://www.enterprisedb.com/docs/pge/18/release_notes/rel_notes18.7.0/
- https://www.enterprisedb.com/docs/epas/15/epas_rel_notes/epas15_20_0_rel_notes/
- https://www.enterprisedb.com/docs/epas/16/epas_rel_notes/epas16_16_0_rel_notes/
- https://www.enterprisedb.com/docs/epas/17/epas_rel_notes/epas17_12_rel_notes/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-87027
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-87027"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • EnterpriseDB EDB Postgres Extended Server

    From 15.0 · fixed in 15.20; From 16.0 · fixed in 16.16; From 17.0 · fixed in 17.12; From 18.0 · fixed in 18.7

  • EnterpriseDB EDB Postgres Advanced Server

    From 15.0 · fixed in 15.20.0; From 16.0 · fixed in 16.16.0; From 17.0 · fixed in 17.12.0; From 18.0 · fixed in 18.7.0

Evidence 11

Vendor advisory · 9

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link
  3. Link
  4. Link
  5. Link
  6. Link
  7. Link
  8. Link
  9. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-87027

Is CVE-2026-87027 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-87027?

EDB Postgres Extended Server: from 15.0 before 15.20; from 16.0 before 16.16; from 17.0 before 17.12; from 18.0 before 18.7. EDB Postgres Advanced Server: from 15.0 before 15.20.0; from 16.0 before 16.16.0; from 17.0 before 17.12.0; from 18.0 before 18.7.0.Source: cve.now feed data

How do I fix CVE-2026-87027?

Upgrade to a fixed version: EDB Postgres Extended Server 15.20, 16.16, 17.12, 18.7 · EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0, 18.7.0.Source: cve.now feed data