CVE-2026-80182

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th 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 — 4 sources updated this weekElevated

Also known asEUVD-2026-66118 (ENISA EUVD) · GHSA-964p-6x56-c2xp (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation restrictions that block these operations did not consistently apply to all delegated token types, allowing an OAuth1-scoped token, for example, to create application credentials or authorize OAuth1 request tokens despite those operations being restricted for other delegated token types. All Keystone deployments that permit delegated authentication through OAuth1 access tokens, application credentials, or trusts are affected.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 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.6% 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 25, 2026

Last Modified

September 9, 2026

Advisory Details (3)

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

oss-security - [OSSA-2026-037] OpenStack Keystone: Inconsistent scope enforcement for delegated tokens (CVE-2026-pending)

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

OSSA-2026-037: Inconsistent scope enforcement for delegated tokens in Keystone — OpenStack Security Advisories 0.0.1.dev384 documentation

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

Bug #2153453 “[OSSA-2026-037] Delegated tokens (ec2credential, O...” : Bugs : OpenStack Identity (keystone)

https://launchpad.net/bugs/2153453

Vendor Advisories for CVE-2026-80182(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
ubuntupython-keystone (2:9.3.0-0ubuntu3.2+esm2) @ xenial2026-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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
keystone2:22.0.0-2, 2:22.0.2-0+deb12u1, 2:22.0.2-0+deb12u2, 2:22.0.2-0+deb12u3
  • every version up to 2:22.0.2-0+deb12u4: fixed in 2:22.0.2-0+deb12u4
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
keystone2:27.0.0-3, 2:27.0.0-3+deb13u1, 2:27.0.0-3+deb13u3, 2:27.0.0-3+deb13u4
  • every version up to 2:27.0.0-3+deb13u5: fixed in 2:27.0.0-3+deb13u5
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
keystone2:27.0.0-3 ... 2:29.0.1-2 (17 versions)
  • every version up to 2:29.0.2-1: fixed in 2:29.0.2-1
—

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

ubuntu:USN-8854-1

Frequently asked(5)

What is CVE-2026-80182?
CVE-2026-80182 is a high-severity vulnerability; its CVE record was published on August 25, 2026. In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new long-lived credentials or authorize new delegations that persist independently of, and outlive, the credential used to obtain them. The delegation…
When was the CVE record for CVE-2026-80182 published?
The CVE record for CVE-2026-80182 was published on August 25, 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-80182 actively exploited?
CVE-2026-80182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80182?
CVE-2026-80182 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80182?
A fix for CVE-2026-80182 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80182 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-80182

Explore →

Is Your Infrastructure Affected by CVE-2026-80182?

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

Book a Demo →Browse All CVEs