CVE-2026-44477
Linuxfoundation Cloudnativepg privilege escalation
- Published28 May 2026
Description
CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.29.1 and 1.28.3, the CloudNativePG metrics exporter opens its PostgreSQL connection as the postgres superuser via the pod-local Unix socket, then demotes the session with SET ROLE pg_monitor. SET ROLE changes only current_user; session_user remains postgres. Any SQL expression evaluated inside the scrape session can invoke RESET ROLE to recover real superuser privileges, then use COPY ... TO PROGRAM to spawn an OS-level subprocess as the postgres user inside the primary pod. The READ ONLY transaction flag does not block this; it gates writes to database state, not external processes. This vulnerability is fixed in 1.29.1 and 1.28.3.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-44477
- https://bugzilla.redhat.com/show_bug.cgi?id=2482763
- https://github.com/cloudnative-pg/cloudnative-pg/pull/10576
- https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-423p-g724-fr39
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44477.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-44477 being actively exploited?
CVE-2026-44477 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.52%.
How severe is CVE-2026-44477?
CVE-2026-44477 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 0.52% probability of exploitation.
Which products are affected by CVE-2026-44477?
Affected products include Linuxfoundation Cloudnativepg.
How do I fix CVE-2026-44477?
Upgrade affected software to a fixed version, for example Linuxfoundation Cloudnativepg 1.29.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-44477 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.