CVE-2026-35430

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Authorization bypass through user-controlled key in Azure Privileged Identity Management (PIM) allows an authorized attacker to elevate privileges over a network.

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
36%
KEV
Not listed

Published

May 22, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Jun 3, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-35430

Vendor Advisories for CVE-2026-35430(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-35430?
CVE-2026-35430 is a high vulnerability published on May 22, 2026. Authorization bypass through user-controlled key in Azure Privileged Identity Management (PIM) allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-35430 disclosed?
CVE-2026-35430 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35430 actively exploited?
CVE-2026-35430 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 63.5% of all scored CVEs.
What is the CVSS score of CVE-2026-35430?
CVE-2026-35430 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-35430?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35430, 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

Explore the affected products and dependency analysis for CVE-2026-35430

Explore →

Is Your Infrastructure Affected by CVE-2026-35430?

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

Start Free Scan →Browse All CVEs