Skip to content
Cloud

CVE-2026-78155

9.9
Critical
EPSS 0.27%Aug 23, 2026

Privilege escalation in StackGres operator lets DB tenants become cluster admins

common questions

Is CVE-2026-78155 being exploited?

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

How severe is CVE-2026-78155?

CVE-2026-78155 is rated Critical with a CVSS score of 9.9. 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-78155?

Not known from our data. No patch reference has been recorded for CVE-2026-78155, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-78155 affect?

CVE-2026-78155 affects StackGres operator, StackGres PostgreSQL operator, Kubernetes clusters running StackGres. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-78155?

Isolate operator, revoke tenant rights, monitor logs, restrict network access, apply vendor patch when released.

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

executive summary
technical analysis
affected
StackGres operatorStackGres PostgreSQL operatorKubernetes clusters running StackGres
impact

Low-privilege DB tenant can escalate to operator/admin, enabling cluster takeover, access to other tenants' DBs, and data exfiltration.

action required

Immediate action required

affected versions
OnGres StackGres
  • affected<= 1.18.8

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