Skip to content
major vulnerability· requires attention

Affects OpenStack core components used widely in public/private clouds; enables cross-project data leakage and remote triggering of orchestration—operational impact for cloud operators.

Cloud

CVE-2026-76878

HIGH
High
EPSS 0.48%Patch availableAug 21, 2026

OpenStack Aodh auth bypass leaks alarms; Watcher webhooks lack auth and can be triggered.

common questions

Is CVE-2026-76878 being exploited?

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

How severe is CVE-2026-76878?

CVE-2026-76878 is rated High. 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-76878?

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

What does CVE-2026-76878 affect?

CVE-2026-76878 affects OpenStack Aodh (< 22.0.1), OpenStack Watcher (since Ussuri / Watcher 4.0.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76878?

Upgrade Aodh to >=22.0.1, enforce auth on Watcher webhooks, rotate exposed URLs/credentials.

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

executive summary
technical analysis
affected
OpenStack Aodh (< 22.0.1)OpenStack Watcher (since Ussuri / Watcher 4.0.0)
impact

Non-admin readers can list alarms across projects exposing webhook/Heat URLs and IDs; attackers can invoke Watcher webhooks to start EVENT audits and action plans.

action required

Immediate action required

affected versions
OpenStack Aodh
  • affected>= 10.0.0 and < 20.0.1
  • affected>= 21.0.0 and < 21.0.1
  • affected>= 22.0.0 and < 22.0.1

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