CVE-2026-55769

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
58(Track*)
EG Risk 58/100SSVC: Track*

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 computed
Severity94% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 21, 2026

Advisory Details (8)

Auto-updated Aug 22, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available

Overriding operators can lead to privilege escalation in CloudNativePG for SQL queries without a fixed `search_path` · Advisory · cloudnative-pg/cloudnative-pg · GitHub

Affected: 1.30.0, 1.29.2, and 1.28.4.

https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-x8c2-3p4r-v9r6
github_release Patch Available

v1.30.0

Patch available: cloudnative-pg/cloudnative-pg v1.30.0

https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.0
github_release Patch Available

v1.29.2

Patch available: cloudnative-pg/cloudnative-pg v1.29.2

https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.29.2
github_release Patch Available

v1.28.4

Patch available: cloudnative-pg/cloudnative-pg v1.28.4

https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.28.4
github_pr

fix(security): pin `search_path` on operator-issued connections

Fix merged in cloudnative-pg/cloudnative-pg PR #10774 on 2026-06-09 — awaiting tagged release

https://github.com/cloudnative-pg/cloudnative-pg/pull/10774
github_commit

commit e0e2d53adbd9 (cloudnative-pg/cloudnative-pg)

Fix landed in cloudnative-pg/cloudnative-pg commit e0e2d53adbd9 — awaiting tagged release

https://github.com/cloudnative-pg/cloudnative-pg/commit/e0e2d53adbd907a61f583b1431904b5969f3fd22
github_commit

commit db38f4d80315 (cloudnative-pg/cloudnative-pg)

Fix landed in cloudnative-pg/cloudnative-pg commit db38f4d80315 — awaiting tagged release

https://github.com/cloudnative-pg/cloudnative-pg/commit/db38f4d80315c8f1b21bf511ef0f28871820c14d
github_commit

commit 02b5c6289b76 (cloudnative-pg/cloudnative-pg)

Fix landed in cloudnative-pg/cloudnative-pg commit 02b5c6289b76 — awaiting tagged release

https://github.com/cloudnative-pg/cloudnative-pg/commit/02b5c6289b7609dc87fcb1ae9c113160e3d43308

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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.

  1. 2026-08-25 13:53 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:31 UTCEG score recompute
  4. 2026-08-24 10:37 UTCEG score recompute
  5. 2026-08-23 03:25 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 00:00 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 12:19 UTCEG score recompute
  10. 2026-08-21 11:30 UTCEG score recompute
  11. 2026-08-20 22:24 UTCEG score recompute
  12. 2026-08-20 21:57 UTCEG score recompute
  13. 2026-08-20 21:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55769?
CVE-2026-55769 is a critical vulnerability published on August 20, 2026. 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 searchpath in fillDefaultParameters in pkg/management/postgres/pool/profiles.go. A role holding DATABASE OWNER…
When was CVE-2026-55769 disclosed?
CVE-2026-55769 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55769 actively exploited?
CVE-2026-55769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55769?
CVE-2026-55769 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-55769?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55769, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55769

Explore →

Is Your Infrastructure Affected by CVE-2026-55769?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.