CVE-2020-12691

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 3.6%, top 12% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
91.1%
KEV
Not listed

Published

May 7, 2020

Last Modified

November 21, 2024

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-keystone (2:13.0.4-0ubuntu1) @ bionic2026-05-27ubuntu
redhatopenstack-keystone-1:16.0.1-0.20200511063421.40cbb7b.el8ost2020-07-22redhat
redhatopenstack-keystone-1:10.0.3-8.el7ost2020-07-22redhat
redhatopenstack-keystone-1:15.0.1-0.20200512110437.95b2bbe.el8ost2020-07-22redhat
redhatopenstack-keystone-1:13.0.4-3.el7ost2020-06-24redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
keystone12.0.2 ... 15.0.0.0rc2 (12 versions)15.0.1

Weakness Classification(1)

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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 7× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:43 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:20 UTCEPSS rescore
  8. 2026-07-05 02:27 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-01 22:01 UTCOSV refresh
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-07-01 15:03 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-28 14:05 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-22 14:23 UTCEPSS rescore
Show 52 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-21 14:54 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-19 19:23 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-15 17:46 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-14 23:15 UTCEPSS rescore
  17. 2026-06-14 03:13 UTCOSV refresh
  18. 2026-06-13 22:58 UTCEPSS rescore
  19. 2026-06-13 22:58 UTCEPSS rescore
  20. 2026-06-12 23:09 UTCEPSS rescore
  21. 2026-06-11 13:58 UTCEPSS rescore
  22. 2026-06-10 22:16 UTCEPSS rescore
  23. 2026-06-10 22:16 UTCEPSS rescore
  24. 2026-06-10 13:20 UTCEPSS rescore
  25. 2026-06-08 14:15 UTCEPSS rescore
  26. 2026-06-08 14:15 UTCEPSS rescore
  27. 2026-06-06 13:45 UTCEPSS rescore
  28. 2026-06-06 13:45 UTCEPSS rescore
  29. 2026-06-06 13:45 UTCEPSS rescore
  30. 2026-06-05 22:45 UTCEPSS rescore
  31. 2026-06-05 22:45 UTCEPSS rescore
  32. 2026-06-05 06:08 UTCEPSS rescore
  33. 2026-06-04 13:10 UTCEPSS rescore
  34. 2026-06-04 13:10 UTCEPSS rescore
  35. 2026-06-02 20:11 UTCEPSS rescore
  36. 2026-06-02 20:11 UTCEPSS rescore
  37. 2026-06-01 13:50 UTCEPSS rescore
  38. 2026-05-31 22:29 UTCEPSS rescore
  39. 2026-05-31 22:29 UTCEPSS rescore
  40. 2026-05-31 00:15 UTCEPSS rescore
  41. 2026-05-31 00:14 UTCEPSS rescore
  42. 2026-05-29 13:42 UTCEPSS rescore
  43. 2026-05-29 13:42 UTCEPSS rescore
  44. 2026-05-28 13:43 UTCEPSS rescore
  45. 2026-05-28 13:43 UTCEPSS rescore
  46. 2026-05-27 13:39 UTCEPSS rescore
  47. 2026-05-27 03:52 UTCEG score recompute
  48. 2026-05-27 03:52 UTCVendor advisory
  49. 2026-05-26 13:42 UTCEPSS rescore
  50. 2026-05-26 13:42 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2020-12691?
CVE-2020-12691 is a high vulnerability published on May 7, 2020. An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user.…
When was CVE-2020-12691 disclosed?
CVE-2020-12691 was first published in the National Vulnerability Database on May 7, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-12691 actively exploited?
CVE-2020-12691 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-12691?
CVE-2020-12691 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2020-12691?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-12691, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-12691

Explore →

Is Your Infrastructure Affected by CVE-2020-12691?

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