CVE-2026-55769
search_path bug allows escalation to PostgreSQL superuser and OS command execution
Is CVE-2026-55769 being exploited?
Not confirmed. CVE-2026-55769 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-55769?
CVE-2026-55769 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55769?
Yes. A fix has been recorded for CVE-2026-55769. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55769 affect?
CVE-2026-55769 affects CloudNativePG <1.28.4, CloudNativePG <1.29.2, PostgreSQL instances managed by CloudNativePG in Kubernetes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55769?
Upgrade to 1.28.4/1.29.2/1.30.0, remove unnecessary DB OWNER roles, rotate pod tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A role with DATABASE OWNER can escalate to PostgreSQL superuser, execute OS commands (COPY ... FROM PROGRAM), and access pod ServiceAccount tokens.
Immediate action required
- affected< 1.28.4
- affected>= 1.29.0 and < 1.29.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.