CVE-2026-35425

HIGHNVD 7.28.0
EchelonGraph scoreMEDIUM confidence

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. NVD baseline CVSS 7.2; sources differ by 0.8.

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

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

Improper access control in Azure API Management (APIM) allows an authorized attacker to execute code over a network.

CVSS v3
7.2
EG Score
8.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity80% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 24, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Jul 24, 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-35425

Vendor Advisories for CVE-2026-35425(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 34× in last 7d / 149× 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 298 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-35425?
CVE-2026-35425 is a high vulnerability published on July 24, 2026. Improper access control in Azure API Management (APIM) allows an authorized attacker to execute code over a network.
When was CVE-2026-35425 disclosed?
CVE-2026-35425 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35425 actively exploited?
CVE-2026-35425 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.8% of all scored CVEs.
What is the CVSS score of CVE-2026-35425?
CVE-2026-35425 has a CVSS v3 base score of 7.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.0.
How do I remediate CVE-2026-35425?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35425, 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-35425

Explore →

Is Your Infrastructure Affected by CVE-2026-35425?

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