CVE-2026-32210

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. the CNA's CVSS baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.3Exploit: None knownExposed: 0

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

Server-side request forgery (ssrf) in Microsoft Dynamics 365 (Online) allows an unauthorized attacker to perform spoofing over a network.

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

Published

April 23, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Sep 14, 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-32210

Vendor Advisories for CVE-2026-32210(1)

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 5× in last 7d / 33× 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 375 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32210?
CVE-2026-32210 is a critical vulnerability published on April 23, 2026. Server-side request forgery (ssrf) in Microsoft Dynamics 365 (Online) allows an unauthorized attacker to perform spoofing over a network.
When was CVE-2026-32210 disclosed?
CVE-2026-32210 was first published in the National Vulnerability Database on April 23, 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-32210 actively exploited?
CVE-2026-32210 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 53.9% of all scored CVEs.
What is the CVSS score of CVE-2026-32210?
CVE-2026-32210 has a CVSS v4.0 base score of 9.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-32210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32210, 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-32210

Explore →

Is Your Infrastructure Affected by CVE-2026-32210?

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

Start Free Scan →Browse All CVEs