Skip to content
Cloud

CVE-2026-55765

8.5
High
EPSS 0.29%Patch availableAug 22, 2026

Cleartext role passwords in CloudNativePG allow tenant to escalate to superuser and run OS commands.

common questions

Is CVE-2026-55765 being exploited?

Not confirmed. CVE-2026-55765 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-55765?

CVE-2026-55765 is rated High with a CVSS score of 8.5. 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-55765?

Yes. A fix has been recorded for CVE-2026-55765. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55765 affect?

CVE-2026-55765 affects CloudNativePG versions prior to 1.28.4 and 1.29.2 (fixed in 1.28.4, 1.29.2, 1.30.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55765?

Upgrade to 1.28.4/1.29.2/1.30.0; disable pg_stat_statements preload or revoke pg_monitor/pg_read_all_stats from tenants.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
CloudNativePG versions prior to 1.28.4 and 1.29.2 (fixed in 1.28.4, 1.29.2, 1.30.0)
impact

Untrusted tenant with pg_monitor/pg_read_all_stats and pg_stat_statements preload can recover managed superuser/app passwords, reconnect as superuser, and run OS commands via COPY ... FROM PROGRAM.

action required

Immediate action required

affected versions
cloudnative-pg cloudnative-pg
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free