CVE-2026-42999

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone RBAC policy enforcer in enforce_call unconditionally merges the raw JSON request body into the policy enforcement dictionary via policy_dict.update(json_input.copy()), overwriting trusted target data that was previously set from database lookups. Because flask.request.get_json is called with force=True, this works regardless of Content-Type or HTTP method. Any authenticated user can inject arbitrary policy target attributes (e.g., user_id, project_id) into the request body to bypass RBAC checks and perform unauthorized operations on resources belonging to other users or projects. This was introduced in commit 5ea59f52 (Rocky/14.0.0).

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 9, 2026
No patch confirmed yet.
generic

OSSA-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.html
generic

Bug #2148398 “[OSSA-2026-015] RBAC Policy Target Injection via J...” : Bugs : OpenStack Identity (keystone)

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

Vendor Advisories for CVE-2026-42999(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 / EcosystemFixed in / PatchReleasedSource
ubuntupython3-keystone (2:28.0.0-0ubuntu1.3) @ questing2026-09-14ubuntu

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 rangeFixed inDependents
keystone2:18.0.0-3, 2:18.0.0-3+deb11u1, 2:18.1.0-1+deb11u22:18.1.0-1+deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
keystone2:22.0.0-2, 2:22.0.2-0+deb12u1, 2:22.0.2-0+deb12u22:22.0.2-0+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
keystone2:27.0.0-3, 2:27.0.0-3+deb13u1, 2:27.0.0-3+deb13u32:27.0.0-3+deb13u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
keystone2:27.0.0-3 ... 2:29.0.1-1 (16 versions)2:29.0.1-2—
PyPI(1)
PackageVulnerable rangeFixed inDependents
keystone14.0.0 ... 29.0.1 (54 versions)29.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 9× in last 7d / 36× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42999?
CVE-2026-42999 is a high vulnerability published on May 28, 2026. An issue was discovered in OpenStack Keystone before 29.0.2. The Keystone RBAC policy enforcer in enforcecall unconditionally merges the raw JSON request body into the policy enforcement dictionary via policydict.update(jsoninput.copy()), overwriting trusted target data that was previously set from…
When was CVE-2026-42999 disclosed?
CVE-2026-42999 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42999 actively exploited?
CVE-2026-42999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-42999?
CVE-2026-42999 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-42999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42999, 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-2026-42999

Explore →

Is Your Infrastructure Affected by CVE-2026-42999?

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

Start Free Scan →Browse All CVEs