CVE-2026-55769: CloudNativePG: Overriding operators can lead to privilege escalation in CloudNativePG for SQL queries without a fixed `search_path`
CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.28.4 and 1.29.2, CloudNativePG opened superuser connections without pinning search_path in fillDefaultParameters in pkg/management/postgres/pool/profiles.go. A role holding DATABASE OWNER could create overloaded built-in operators in the public schema and change the database or role search_path, causing instance-manager introspection queries such as SELECT COUNT(*) > 0 FROM pg_catalog.pg_extension WHERE extname = $1 to execute attacker-controlled functions as the postgres superuser. The same trust issue affected direct sql.Open("pgx", ...) callsites and the public.user_search SECURITY DEFINER function, enabling PostgreSQL superuser access, operating system command execution through COPY ... FROM PROGRAM, and access to the pod ServiceAccount token. This issue is fixed in versions 1.28.4, 1.29.2, and 1.30.0.
Security readout for executives and security teams
Plain-English summary
A database owner in a vulnerable CloudNativePG cluster could turn limited database access into PostgreSQL superuser privileges. The resulting control could expose or alter all database data, execute operating-system commands inside the database pod, and access its Kubernetes ServiceAccount token, potentially expanding impact beyond PostgreSQL.
Executive priority
Treat remediation as immediate for internet-facing, multi-tenant, or delegated-ownership databases. The vulnerability can convert a comparatively limited database role into control over data, the PostgreSQL service, and potentially Kubernetes credentials. Prioritize inventory and upgrades, then investigate higher-risk clusters for evidence of abuse.
Technical view
CloudNativePG superuser connections and a SECURITY DEFINER function did not consistently fix PostgreSQL search_path. An attacker with DATABASE OWNER privileges could exploit operator resolution in a writable schema, causing privileged introspection queries to invoke attacker-controlled functions. The flaw affects releases before 1.28.4 and releases from 1.29.0 through 1.29.1.
Likely exposure
Exposure requires a vulnerable CloudNativePG version and a database principal able to issue SQL with DATABASE OWNER privileges. Risk is greatest where database ownership is delegated to application teams, tenants, automation, or other principals not trusted with cluster, pod, or Kubernetes credentials.
Exploitation context
The source bundle does not report known exploitation in the wild, and the CVE is not identified as being in CISA KEV. Exploitation nevertheless has low stated complexity, requires no user interaction, and can cross database, operating-system, and Kubernetes trust boundaries.
Researcher notes
This is a CWE-426 untrusted search-path problem involving operator overloading and privileged query resolution. The advisory identifies affected pooled superuser connections, direct pgx connection sites, and public.user_search. Fixes are published in 1.28.4, 1.29.2, and 1.30.0; the supplied evidence does not establish exploitation prevalence.
Mitigation direction
Upgrade 1.28 deployments to 1.28.4 or later, and 1.29 deployments to 1.29.2 or later.
Use 1.30.0 or another vendor-confirmed fixed release when moving to the 1.30 branch.
Until upgraded, limit DATABASE OWNER and SQL access to fully trusted principals.
Review the vendor advisory for supported upgrade and interim risk-reduction guidance.
If compromise is suspected, investigate before rotating exposed database and Kubernetes credentials.
Validation and detection
Inventory CloudNativePG versions across every Kubernetes cluster and namespace.
Confirm no deployment remains below 1.28.4 or on versions 1.29.0 through 1.29.1.
Identify every role holding DATABASE OWNER and determine whether each principal is fully trusted.
Review available audit history for unexpected search_path changes or objects created in writable schemas.
Investigate anomalous PostgreSQL superuser activity, pod command execution, and ServiceAccount token access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-426: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-426 · source CWE mapping
Untrusted Search Path
Untrusted Search Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.