CVE-2026-76878

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2026-63137 (ENISA EUVD) · GHSA-25rc-jgc5-f99w (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
Patch available.
Web page

oss-security - [OSSA-2026-036] OpenStack Aodh and Watcher: Aodh cross-project alarm enumeration and Watcher webhook authorization bypass (CVE-2026-pending)

https://www.openwall.com/lists/oss-security/2026/08/19/5
Web page

[OSSA-2026-036] OpenStack Aodh and Watcher: Aodh cross-project alarm enumeration and Watcher webhook authorization bypass (CVE-2026-pending) - OpenStack-announce - lists.openstack.org

https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/O6PKAUNMNZP6FRHLUUGBYELCRBEPB52B/
Web page

OSSA-2026-036: Aodh cross-project alarm enumeration and Watcher webhook authorization bypass — OpenStack Security Advisories 0.0.1.dev373 documentation

https://security.openstack.org/ossa/OSSA-2026-036.html
Web page

Bug #2161771 “[OSSA-2026-036] Watcher Lets an Unrelated Authenti...” : Bugs : OpenStack Security Advisory

https://launchpad.net/bugs/2161771
Web page

Bug #2161276 “[OSSA-2026-036] Aodh all_projects=false bypasses p...” : Bugs : OpenStack Security Advisory

https://launchpad.net/bugs/2161276

Vendor Advisories for CVE-2026-76878(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuwatcher-doc (2:16.0.0-0ubuntu1+esm1) @ resolute2026-10-28ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
aodh15.0.0-3 ... 23.0.0~rc1-2 (37 versions)
  • every version on: no fix on record
—
watcher10.0.0-1 ... 9.0.0-2 (37 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
aodh20.0.0-2 ... 23.0.0~rc1-2 (19 versions)
  • every version on: no fix on record
—
watcher14.0.0-1 ... 17.0.0~rc1-2 (22 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
aodh20.0.0-2 ... 22.0.0~rc1-5 (14 versions)
  • every version up to 22.0.0-3: fixed in 22.0.0-3
—
watcher14.0.0-1 ... 16.0.0~rc1-4 (16 versions)
  • every version up to 16.0.0-5: fixed in 16.0.0-5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-10-28 23:04 UTCEG score recompute
  7. 2026-10-28 23:04 UTCVendor advisory
  8. 2026-10-28 23:04 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  9. 2026-10-28 20:25 UTCOSV refresh
  10. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-25 14:01 UTCEG score recompute
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-21 00:00 UTCEG score recompute
  20. 2026-10-21 00:00 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-18 03:12 UTCEG score recompute
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-13 07:03 UTCEG score recompute
  6. 2026-10-13 07:03 UTCVendor advisory
  7. 2026-10-13 07:03 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  8. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-12 15:38 UTCEG score recompute
  10. 2026-10-11 19:23 UTCEG score recompute
  11. 2026-10-11 16:39 UTCEG score recompute
  12. 2026-10-11 13:58 UTCEG score recompute
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-08 05:56 UTCEG score recompute
  18. 2026-10-08 05:56 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-07 04:47 UTCVendor advisory
  21. 2026-10-07 04:47 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  22. 2026-10-06 16:57 UTCEG score recompute
  23. 2026-10-06 16:57 UTCVendor advisory
  24. 2026-10-06 16:57 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-10-06 03:39 UTCEG score recompute
  27. 2026-10-06 03:39 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  28. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-10-05 09:31 UTCEG score recompute
  30. 2026-10-05 09:31 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  31. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-04 21:21 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  33. 2026-10-04 05:06 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  34. 2026-10-03 16:51 UTCEG score recompute
  35. 2026-10-03 16:51 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-10-02 21:35 UTCEG score recompute
  38. 2026-10-02 21:35 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  39. 2026-10-02 09:22 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  40. 2026-10-01 21:33 UTCEG score recompute
  41. 2026-10-01 21:33 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-10-01 08:25 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  44. 2026-09-30 20:33 UTCEG score recompute
  45. 2026-09-30 20:33 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  46. 2026-09-30 08:28 UTCEG score recompute
  47. 2026-09-30 08:28 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  48. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  49. 2026-09-28 21:40 UTCEG score recompute
  50. 2026-09-28 21:40 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  51. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-09-28 03:56 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  53. 2026-09-27 16:05 UTCEG score recompute
  54. 2026-09-27 16:04 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  55. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  56. 2026-09-27 04:15 UTCEG score recompute
  57. 2026-09-27 04:15 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  58. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  59. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  60. 2026-09-25 12:50 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  61. 2026-09-25 01:01 UTCEG score recompute
  62. 2026-09-25 01:01 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  63. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  64. 2026-09-24 13:11 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  65. 2026-09-24 01:22 UTCEG score recompute
  66. 2026-09-24 01:22 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  67. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  68. 2026-09-23 13:32 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  69. 2026-09-23 01:43 UTCEG score recompute
  70. 2026-09-23 01:43 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  71. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  72. 2026-09-22 13:53 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  73. 2026-09-22 02:03 UTCEG score recompute
  74. 2026-09-22 02:02 UTCGHSA enrichmentGHSA-25rc-jgc5-f99w · GitHub severity HIGH
  75. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 40th percentile

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:12:aodh

Frequently asked(5)

What is CVE-2026-76878?
CVE-2026-76878 is a high-severity vulnerability; its CVE record was published on August 19, 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. 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…
When was the CVE record for CVE-2026-76878 published?
The CVE record for CVE-2026-76878 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-76878 actively exploited?
CVE-2026-76878 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76878?
CVE-2026-76878 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76878?
A fix for CVE-2026-76878 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76878 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76878

Explore →

Is Your Infrastructure Affected by CVE-2026-76878?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs