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.
CVE-2026-80182
“—” 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% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.6
- EG Score
- 7.6HIGHmedium confidence
- EG Risk
- 50EG Risk 50/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity76% × 45%The EG Score, 7.6 of 10.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
- 45th
- KEV
- Not listed
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.
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, 2026oss-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/5OSSA-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.htmlBug #2153453 “[OSSA-2026-037] Delegated tokens (ec2credential, O...” : Bugs : OpenStack Identity (keystone)
https://launchpad.net/bugs/2153453Vendor 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 / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3-keystone (2:21.0.1-0ubuntu2.6) @ jammy | 2026-10-10 | ubuntu |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| keystone | 2:22.0.0-2, 2:22.0.2-0+deb12u1, 2:22.0.2-0+deb12u2, 2:22.0.2-0+deb12u3 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| keystone | 2:27.0.0-3, 2:27.0.0-3+deb13u1, 2:27.0.0-3+deb13u3, 2:27.0.0-3+deb13u4 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| keystone | 2:27.0.0-3 ... 2:29.0.1-2 (17 versions) |
| — |
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 22× in last 7d / 122× 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 200 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 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-13 06:32 UTCEG score recompute
- 2026-10-13 06:32 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-12 14:57 UTCEG score recompute
- 2026-10-11 19:21 UTCEG score recompute
- 2026-10-11 16:37 UTCEG score recompute
- 2026-10-11 13:56 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-10 11:11 UTCEG score recompute
- 2026-10-10 11:11 UTCVendor advisory
- 2026-10-10 11:11 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-09 03:42 UTCEG score recompute
- 2026-10-09 03:42 UTCVendor advisory
- 2026-10-09 03:42 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-08 02:17 UTCEG score recompute
- 2026-10-08 02:17 UTCVendor advisory
- 2026-10-08 02:17 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-07 07:11 UTCVendor advisory
- 2026-10-07 07:11 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-06 19:25 UTCEG score recompute
Show 75 moreShow fewer
- 2026-10-06 19:25 UTCVendor advisory
- 2026-10-06 19:25 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-06 07:39 UTCEG score recompute
- 2026-10-06 07:39 UTCVendor advisory
- 2026-10-06 07:39 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-05 16:58 UTCVendor advisory
- 2026-10-05 16:58 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-05 03:48 UTCEG score recompute
- 2026-10-05 03:48 UTCVendor advisory
- 2026-10-05 03:47 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-04 16:01 UTCVendor advisory
- 2026-10-04 16:01 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-04 04:02 UTCVendor advisory
- 2026-10-04 04:02 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-03 16:17 UTCEG score recompute
- 2026-10-03 16:17 UTCVendor advisory
- 2026-10-03 16:17 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-02 19:44 UTCEG score recompute
- 2026-10-02 19:44 UTCVendor advisory
- 2026-10-02 19:44 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-02 07:59 UTCVendor advisory
- 2026-10-02 07:59 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-01 19:59 UTCEG score recompute
- 2026-10-01 19:59 UTCVendor advisory
- 2026-10-01 19:59 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-01 07:54 UTCVendor advisory
- 2026-10-01 07:54 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-30 20:09 UTCEG score recompute
- 2026-09-30 20:09 UTCVendor advisory
- 2026-09-30 20:09 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-30 06:22 UTCEG score recompute
- 2026-09-30 06:22 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-29 12:40 UTCEG score recompute
- 2026-09-29 12:40 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-28 21:24 UTCEG score recompute
- 2026-09-28 21:24 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-28 09:01 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-27 21:15 UTCEG score recompute
- 2026-09-27 21:15 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-27 09:30 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-26 21:37 UTCEG score recompute
- 2026-09-26 21:37 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-09-25 09:58 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-24 22:12 UTCEG score recompute
- 2026-09-24 22:12 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
- 2026-09-24 10:19 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-23 22:34 UTCEG score recompute
- 2026-09-23 22:34 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-23 10:48 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-22 22:48 UTCEG score recompute
- 2026-09-22 22:48 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-22 11:02 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-21 23:17 UTCEG score recompute
- 2026-09-21 23:17 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-21 11:30 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-20 23:44 UTCEG score recompute
- 2026-09-20 23:44 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-20 11:58 UTCGHSA enrichmentGHSA-964p-6x56-c2xp · GitHub severity HIGH
- 2026-09-19 23:58 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:12:keystone
Frequently asked(5)
What is CVE-2026-80182?
When was the CVE record for CVE-2026-80182 published?
Is CVE-2026-80182 actively exploited?
What is the CVSS score of CVE-2026-80182?
How do I remediate CVE-2026-80182?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80182
Is Your Infrastructure Affected by CVE-2026-80182?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.