CVE-2026-43001

HIGHNVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied project_id for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential for project A to create an EC2 credential targeting project B; a subsequent /v3/ec2tokens exchange would then issue a Keystone token scoped to project B while still carrying the original app_cred_id, enabling cross-project lateral movement within the credential owner's role footprint.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
36
EG Risk 36/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
Severity80% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

Published

May 1, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated May 1, 2026
Patch available.
generic
https://review.opendev.org/c/openstack/keystone/+/985804
generic

Bug #2149775 “Generic EC2 credential creation allows application...” : Bugs : OpenStack Identity (keystone)

https://bugs.launchpad.net/keystone/+bug/2149775

Vendor Advisories for CVE-2026-43001(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhosp-rhel8/openstack-keystone:1:16.0.3-2.20260616134936.9d699a7.el8ost2026-08-13redhat
redhatopenstack-keystone-1:23.0.3-18.0.20260610133808.9e3dfb4.el9ost2026-07-15redhat
pipkeystone—ghsa

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
keystone2:18.0.0-3, 2:18.0.0-3+deb11u1, 2:18.1.0-1+deb11u2
  • every version up to 2:18.1.0-1+deb11u3: fixed in 2:18.1.0-1+deb11u3
—
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
  • every version up to 2:22.0.2-0+deb12u3: fixed in 2:22.0.2-0+deb12u3
—
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
  • every version up to 2:27.0.0-3+deb13u4: fixed in 2:27.0.0-3+deb13u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
keystone2:27.0.0-3 ... 2:29.0.1-1 (16 versions)
  • every version up to 2:29.0.1-2: fixed in 2:29.0.1-2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
keystone14.0.0 ... 29.0.1 (54 versions)
  • 13.0.0 through 29.0.1: no fix on record
  • 14.0.0 up to 27.0.2: fixed in 27.0.2
  • 28.0.0 up to 28.0.2: fixed in 28.0.2
  • 29.0.0 up to 29.0.2: fixed in 29.0.2
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× 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 236 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-43001?
CVE-2026-43001 is a high vulnerability published on May 1, 2026. An issue was discovered in OpenStack Keystone before 29.0.2. POST /v3/credentials did not validate that the caller-supplied projectid for an EC2-type credential matched the project of the authenticating application credential. This allowed an attacker holding an unrestricted application credential…
When was CVE-2026-43001 disclosed?
CVE-2026-43001 was first published on May 1, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43001 actively exploited?
CVE-2026-43001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43001?
CVE-2026-43001 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-43001?
A fix for CVE-2026-43001 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43001 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-43001

Explore →

Is Your Infrastructure Affected by CVE-2026-43001?

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

Book a Demo →Browse All CVEs