CVE-2026-96538: WarehousePG pg_file_write/pg_file_rename/pg_file_unlink/pg_logdir_ls privilege escalation

Published Sep 28, 2026
·
Updated

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 pgfilewrite(text,text,bool), pgfilerename(text,text,text), pgfileunlink(text), and pglogdirls(). 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 pgfilewrite, pgfilerename, and pgfileunlink to create, overwrite (append), rename, and delete files under the data and log directories, and can use pglogdirls() to enumerate log file names. Because postgresql.auto.conf resides in the data directory, a non-superuser can append configuration directives such as sharedpreloadlibraries or archivecommand 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.

Affected Software

1 affected component
WarehousePG WarehousePG<7.6.0-WHPG

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WarehousePG to a version that resolves this vulnerability.

    Fixed in 7.6.0-WHPG

Event History

Sep 28, 2026
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
DescriptionWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

WarehousePG 7.x releases before 7.6.0-WHPG are affected. WarehousePG 6.x is not affected because its equivalent functions enforce authorization checks.

2

Does an attacker need elevated database privileges or an explicit GRANT?

No. Any authenticated database role, including a non-superuser, can execute the affected functions without an explicit GRANT.

3

What can a low-privileged database user do with this access?

They can create, append to, rename, or delete files under the data and log directories, and enumerate log file names. They can append directives to postgresql.auto.conf and obtain code execution as the postgres operating-system user after a server restart or configuration reload.

4

Is a default installation exposed?

Yes. The affected functions are executable by authenticated roles without a GRANT because the intended REVOKE was not carried over into WarehousePG core.

5

What version should be used to remediate the issue?

Upgrade affected WarehousePG 7.x deployments to 7.6.0-WHPG or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203