CVE-2026-47643

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

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

External control of file name or path in Azure Stack Edge allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
51.2%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 16, 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-47643

Vendor Advisories for CVE-2026-47643(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-47643?
CVE-2026-47643 is a critical vulnerability published on June 9, 2026. External control of file name or path in Azure Stack Edge allows an unauthorized attacker to execute code over a network.
When was CVE-2026-47643 disclosed?
CVE-2026-47643 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47643 actively exploited?
CVE-2026-47643 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47643?
CVE-2026-47643 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47643?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47643, 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-47643

Explore →

Is Your Infrastructure Affected by CVE-2026-47643?

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