CVE-2026-55765: CloudNativePG: Cleartext role passwords recorded in pg_stat_statements allow privileged tenant roles to recover the PostgreSQL superuser credential and achieve RCE in the database pod

Published Aug 20, 2026
·
Updated

CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.28.4 and 1.29.2, CloudNativePG embedded cleartext role passwords in ALTER ROLE and CREATE ROLE statements generated by SetUserPassword in pkg/management/postgres/utils/roles.go and appendPasswordOption in internal/management/controller/roles/postgres.go. When pgstatstatements was preloaded with trackutility enabled and an untrusted tenant held pgmonitor or pgreadallstats, the tenant could recover platform-managed superuser or application-owner passwords, reconnect through enabled superuser TCP access, and execute operating system commands in the database pod with COPY ... FROM PROGRAM. Clusters using SCRAM-SHA-256 verifiers in managed-role Secrets were not affected. This issue is fixed in versions 1.28.4, 1.29.2, and 1.30.0.

Affected Software

1 affected component
CloudNativePG CloudNativePG>0<1.28.4, >1.28.4<1.29.2, >1.29.2<=1.30.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade CloudNativePG to a version that resolves this vulnerability.

    Fixed in 1.28.4
  2. Upgrade

    Upgrade CloudNativePG to a version that resolves this vulnerability.

    Fixed in 1.29.2
  3. Upgrade

    Upgrade CloudNativePG to a version that resolves this vulnerability.

    Fixed in 1.30.0

Event History

Aug 20, 2026
CVE Published
via MITRE·09:38 PM
Data Sourced
via MITRE·09:38 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Affected deployments are CloudNativePG versions before 1.28.4 or 1.29.2 where pg_stat_statements is preloaded with track_utility enabled, an untrusted tenant has pg_monitor or pg_read_all_stats, and superuser TCP access is enabled. Deployments whose managed-role Secrets use SCRAM-SHA-256 verifiers are not affected.

2

What access does an attacker need?

The attacker needs a tenant role that is not trusted but has either pg_monitor or pg_read_all_stats. They also need the affected pg_stat_statements configuration to retrieve cleartext passwords recorded in role-management utility statements.

3

What can an attacker do after recovering a password?

A recovered platform-managed superuser or application-owner password can be used to reconnect through enabled superuser TCP access. The attacker can then execute operating-system commands in the database pod using COPY ... FROM PROGRAM.

4

What versions fix the issue?

The issue is fixed in CloudNativePG 1.28.4, 1.29.2, and 1.30.0.

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