RCE on widely deployed edge hardware could disrupt edge workloads across many orgs.
CVE-2026-47643
RCE on Azure Stack Edge via external file/path control.
Is CVE-2026-47643 being exploited?
Not confirmed. CVE-2026-47643 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.75% probability of exploitation in the next 30 days.
How severe is CVE-2026-47643?
CVE-2026-47643 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47643?
Yes. A fix has been recorded for CVE-2026-47643. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47643 affect?
CVE-2026-47643 affects Azure Stack Edge. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47643?
Apply available firmware patch; isolate affected devices; monitor traffic.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on edge device via crafted file name/path input over network.
Immediate action required
- affected>= 2.2.0 and < 3.3.2604.3097
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.