GHSA-JQ42-R65F-4JXP
Vulnerability from github – Published: 2026-11-16 21:31 – Updated: 2026-11-16 21:31In 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": [],
"aliases": [
"CVE-2026-87027"
],
"database_specific": {
"cwe_ids": [
"CWE-331"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-16T19:17:53Z",
"severity": "MODERATE"
},
"details": "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\u0027s 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.",
"id": "GHSA-jq42-r65f-4jxp",
"modified": "2026-11-16T21:31:40Z",
"published": "2026-11-16T21:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-87027"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/epas/15/epas_rel_notes/epas15_20_0_rel_notes"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/epas/16/epas_rel_notes/epas16_16_0_rel_notes"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/epas/17/epas_rel_notes/epas17_12_rel_notes"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/epas/18/epas_rel_notes/epas18_7_rel_notes"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/pge/15/release_notes/rel_notes15.20"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/pge/16/release_notes/rel_notes16.16"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/pge/17/release_notes/rel_notes17.12"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/pge/18/release_notes/rel_notes18.7.0"
},
{
"type": "WEB",
"url": "https://www.enterprisedb.com/docs/security/advisories/cve202687027"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.