An issue was discovered in OpenStack Keystone before 29.0.2. When combined with an application credential impersonation vulnerability, an attacker with the member role on a project can escalate to admin by chaining unrestricted application credentials with Keystone trusts. The impersonated token carries the victim's identity, which passes the trustor validation check. Keystone then validates the delegated roles against the victim's actual role assignments in the database, not the roles on the requesting token. This allows the attacker to create a trust delegating the victim's admin role to themselves. The trust persists independently, and additional trusts and application credentials can be created to maintain access. All actions are logged under the victim's identity.
CVE-2026-43000
Score 6.0 from GitHub Security Advisory published 2026-05-28. NVD baseline CVSS 8.8; sources differ by 2.8.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 6.0(medium)
- EPSS
- 24.8%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
July 15, 2026
Advisory Details (2)
Auto-updated Jun 9, 2026OSSA-2026-015: Multiple credential delegation and authorization bypass vulnerabilities in Keystone — OpenStack Security Advisories 0.0.1.dev342 documentation
https://security.openstack.org/ossa/OSSA-2026-015.htmlBug #2148477 “[OSSA-2026-015] Impersonation via application cred...” : Bugs : OpenStack Identity (keystone)
https://bugs.launchpad.net/keystone/+bug/2148477Vendor Advisories for CVE-2026-43000(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 | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3-keystone (2:28.0.0-0ubuntu1.3) @ questing | 2026-07-11 | 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
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| keystone | 14.0.0 ... 27.0.1 (50 versions) | 27.0.2 | — |
Weakness Classification(2)
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 / 69× 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.
Showing the most recent 100 of 131 total refreshes for this CVE.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:26 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 6 · severity → MEDIUM
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 22:35 UTCEG score recompute
- 2026-07-11 22:35 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 22:50 UTCEG score recompute
- 2026-07-08 22:50 UTCVendor advisory
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-02 23:31 UTCEG score recompute
- 2026-07-02 23:31 UTCVendor advisory
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 03:46 UTCEG score recompute
- 2026-07-01 03:46 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-01 03:46 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 22:08 UTCEG score recompute
- 2026-06-29 22:08 UTCVendor advisory
- 2026-06-29 22:08 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 22:22 UTCEG score recompute
- 2026-06-28 22:22 UTCVendor advisory
- 2026-06-28 22:22 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 22:40 UTCEG score recompute
- 2026-06-27 22:40 UTCVendor advisory
- 2026-06-27 22:40 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 22:58 UTCEG score recompute
- 2026-06-26 22:58 UTCVendor advisory
- 2026-06-26 22:57 UTCGHSA enrichment
- 2026-06-25 22:52 UTCEG score recompute
- 2026-06-25 22:52 UTCVendor advisory
- 2026-06-25 22:52 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 23:10 UTCEG score recompute
- 2026-06-24 23:10 UTCVendor advisory
- 2026-06-24 23:10 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 21:11 UTCEG score recompute
- 2026-06-17 21:11 UTCVendor advisory
- 2026-06-17 21:10 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 21:25 UTCEG score recompute
- 2026-06-16 21:25 UTCVendor advisory
- 2026-06-16 21:25 UTCGHSA enrichment
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 21:43 UTCEG score recompute
- 2026-06-15 21:43 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-14 21:03 UTCEG score recompute
- 2026-06-14 21:03 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 21:22 UTCEG score recompute
- 2026-06-13 21:22 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 21:40 UTCEG score recompute
- 2026-06-12 21:40 UTCGHSA enrichment
- 2026-06-11 21:59 UTCEG score recompute
- 2026-06-11 21:59 UTCGHSA enrichment
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 22:18 UTCEG score recompute
- 2026-06-10 22:18 UTCGHSA enrichment
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-09 22:36 UTCEG score recompute
- 2026-06-09 22:36 UTCGHSA enrichment
- 2026-06-08 23:31 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
- 2026-06-08 22:55 UTCEG score recompute
- 2026-06-08 22:55 UTCGHSA enrichment
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-07 23:13 UTCEG score recompute
- 2026-06-07 23:13 UTCGHSA enrichment
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-43000?
When was CVE-2026-43000 disclosed?
Is CVE-2026-43000 actively exploited?
What is the CVSS score of CVE-2026-43000?
How do I remediate CVE-2026-43000?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43000
Is Your Infrastructure Affected by CVE-2026-43000?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.