CVE-2026-76878

published 19 Aug 2026 · updated 12 Nov 2026

In OpenStack Aodh before 22.0.1, the alarm list API bypasses project scoping when the all_projects query parameter is set to false

8.4HighCVSS 8.4EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 20.0.1, 21.0.1 and 22.0.1.

In OpenStack Aodh before 22.0.1, the alarm list API bypasses project scoping when the all_projects query parameter is set to false. The API checks for the presence of the all_projects key rather than its value; a true value enforces the administrator-only policy, but a false value removes the key and skips the branch that normally restricts results to the caller's project. A non-admin user with the reader role can list alarms from all projects, exposing alarm actions containing trust webhook URLs, Heat signal endpoints, project IDs, and user IDs. The parameter can also be combined with a foreign project_id to target a specific project's alarms. A related concern is that OpenStack Watcher does not apply authorization to its webhook trigger endpoint. Any authenticated user who learns an audit's webhook URL, for example from this leaked Aodh alarm metadata, can start an EVENT audit and its associated action plan regardless of their own project or role. The webhook endpoint has lacked policy enforcement since its introduction in the Ussuri release (Watcher 4.0.0).

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
OpenStack>=10.0.0 <20.0.1, >=21.0.0 <21.0.1, >=22.0.0 <22.0.120.0.1, 21.0.1, 22.0.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76878 severity on Zeptric[![CVE-2026-76878](https://zeptric.io/badge/cve/CVE-2026-76878.svg)](https://zeptric.io/cve/CVE-2026-76878)