WarehousePG (WHPG) 7.x before 7.6.0-WHPG is affected by a missing authorization vulnerability (CWE-862) in the built-in server-side file functions pg_file_write(text,text,bool), pg_file_rename(text,text,text), pg_file_unlink(text), and pg_logdir_ls(). These functions are executable by any authenticated database role with no GRANT required, because the REVOKE that contrib/adminpack applies to the equivalent functions was never carried over to WHPG core when their catalog entries were repointed to the ungated adminpack-derived implementations as part of Greenplum's merge to a PostgreSQL 12 base. A non-superuser can use pg_file_write, pg_file_rename, and pg_file_unlink to create, overwrite (append), rename, and delete files under the data and log directories, and can use pg_logdir_ls() to enumerate log file names. Because postgresql.auto.conf resides in the data directory, a non-superuser can append configuration directives such as shared_preload_libraries or archive_command to it, resulting in arbitrary code execution as the postgres operating system user on the next server restart or configuration reload. WarehousePG 6.x is not affected, as the equivalent functions there enforce a superuser check internally.
CVE-2026-96538
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 39EG Risk 39/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 23rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 28, 2026
Last Modified
September 30, 2026
Advisory Details (2)
Auto-updated Sep 28, 2026EDB Docs - CVE-2026-96538 - WarehousePG pg_file_write/pg_file_rename/pg_file_unlink privilege escalation
https://www.enterprisedb.com/docs/security/advisories/cve202696538Require superuser or pg_write_server_files for pg_file_write/rename/unlink
Fix merged in warehouse-pg/warehouse-pg PR #305 on 2026-09-22 — awaiting tagged release
https://github.com/warehouse-pg/warehouse-pg/pull/305Vendor Advisories for CVE-2026-96538(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 31× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-05 01:46 UTCEG score recompute
- 2026-10-05 01:46 UTCGHSA enrichment
- 2026-10-04 23:23 UTCEPSS rescore
- 2026-10-04 13:05 UTCGHSA enrichment
- 2026-10-04 00:21 UTCEG score recompute
- 2026-10-04 00:21 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 11:41 UTCGHSA enrichment
- 2026-10-02 22:46 UTCEG score recompute
- 2026-10-02 22:46 UTCGHSA enrichment
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-02 10:04 UTCGHSA enrichment
- 2026-10-01 21:23 UTCEG score recompute
- 2026-10-01 21:23 UTCGHSA enrichment
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-10-01 08:42 UTCGHSA enrichment
- 2026-09-30 20:02 UTCEG score recompute
- 2026-09-30 20:02 UTCGHSA enrichment
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-30 07:43 UTCGHSA enrichment
- 2026-09-29 18:58 UTCEG score recompute
- 2026-09-29 18:58 UTCGHSA enrichment
- 2026-09-29 06:15 UTCEG score recompute
- 2026-09-29 06:15 UTCGHSA enrichment
- 2026-09-28 17:35 UTCEG score recompute
Show 6 moreShow fewer
- 2026-09-28 17:34 UTCGHSA enrichment
- 2026-09-28 16:34 UTCEG score recompute
- 2026-09-28 16:33 UTCGHSA enrichment
- 2026-09-28 15:27 UTCEG score recompute
- 2026-09-28 14:57 UTCEG score recompute
- 2026-09-28 14:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-96538?
When was CVE-2026-96538 disclosed?
Is CVE-2026-96538 actively exploited?
What is the CVSS score of CVE-2026-96538?
How do I remediate CVE-2026-96538?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96538
Is Your Infrastructure Affected by CVE-2026-96538?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.