Skip to main content

OpenStack Aodh CVE-2026-76878

| EUVDEUVD-2026-63137 HIGH
Function Call With Incorrect Variable or Reference as Argument (CWE-688)
2026-08-19 cve@mitre.org GHSA-25rc-jgc5-f99w
8.4
CVSS 4.0 · Vendor: mitre
Share

Severity by source

Vendor (mitre) PRIMARY
8.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
9.6 CRITICAL

PR:L confirmed by reader-role requirement; S:C and I:H reflect cross-system Watcher action plan execution; A:N as no availability impact is described.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:H/SA:N
Red Hat
6.3 MEDIUM
qualitative

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

3
Patch available
Aug 19, 2026 - 23:04 EUVD
Analysis Generated
Aug 19, 2026 - 22:36 vuln.today
CVE Published
Aug 19, 2026 - 22:17 cve.org
HIGH 8.4

DescriptionCVE.org

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).

AnalysisAI

Authorization bypass in OpenStack Aodh's alarm list API allows any authenticated user with the reader role to enumerate alarms across all projects by exploiting a logic flaw where passing all_projects=false removes the project-scoping key entirely rather than restricting scope - exposing trust webhook URLs, Heat signal endpoints, project IDs, and user IDs from foreign projects. The leaked webhook URLs directly enable a second-stage attack against OpenStack Watcher, whose webhook trigger endpoint has enforced no authorization since the Ussuri release (Watcher 4.0.0), permitting any authenticated user who obtains a webhook URL to start EVENT audits and execute associated action plans against arbitrary projects. No public exploit code or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 score of 8.4 reflects the chained confidentiality-then-cross-system-integrity impact of these two related flaws.

Technical ContextAI

OpenStack Aodh is the telemetry alarming service within the OpenStack ecosystem, providing alarm management via a REST API. The vulnerability (CWE-688: Function Call With Incorrect Variable or Reference as Argument) stems from the API handler checking for the mere presence of the all_projects query parameter key rather than evaluating its boolean value: supplying all_projects=true causes the code to enter a branch that enforces an administrator-only policy, but supplying all_projects=false causes the key to be absent from the internal parameter map, silently bypassing the authorization check and returning all alarms globally. This class of boolean-handling error is common in query-parameter parsing logic that conflates key absence with false. The secondary issue in OpenStack Watcher (the optimization service) is a separate missing-authorization defect: its EVENT audit webhook trigger endpoint, introduced in Watcher 4.0.0 (Ussuri cycle), was never gated by any policy enforcement, making it callable by any authenticated user who possesses the URL. The two flaws chain: Aodh leaks Watcher webhook URLs, and Watcher's endpoint enforces no access control on those URLs. Affected versions per the advisory are OpenStack Aodh before 22.0.1, and OpenStack Watcher from 4.0.0 through at least the version current at disclosure.

RemediationAI

Upgrade OpenStack Aodh to version 22.0.1 or later, which is the vendor-confirmed fix version per the description and the OSSA-2026-036 advisory at https://security.openstack.org/ossa/OSSA-2026-036.html. Consult the same advisory and the Launchpad bug at https://launchpad.net/bugs/2161771 for the corresponding patched version of OpenStack Watcher; the Watcher fix version was not independently specified in available input data. As a compensating control prior to patching, operators should restrict the Aodh alarm list API endpoint at the network or load-balancer level so that only administrator-privileged service accounts can reach it, accepting the trade-off that legitimate reader-role users will lose alarm visibility. For Watcher, the webhook trigger endpoint path should be blocked via API gateway policy or firewall rules until the policy enforcement patch is applied, with the trade-off that Heat/Ceilometer-triggered audits using those webhooks will fail. Operators should also audit existing alarm definitions for any trust webhook URLs or Heat signal endpoints in the alarm_actions fields that may already have been exposed to non-admin users, and rotate any credentials or tokens embedded in those URLs.

Vendor StatusVendor

Share

CVE-2026-76878 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy