Vulnary
← back to the feed
Critical· 9.8

CVE-2026-47643

This vulnerability allows an attacker to control file names or paths on Azure Stack Edge, enabling remote code execution. It is critical because it can be exploited over the network without authentication. The flaw arises from improper validation of file paths.

publishedJun 9, 2026
last modifiedJul 23, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
51th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 6, 2026

No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.

01

Who is affected

Microsoft Azure Stack Edge devices, any version that has not applied a patch.

02

Real-world impact

An attacker could run arbitrary code on the device, potentially taking control of the system, exfiltrating data, or using it as a pivot point.

03

Why this severity

The CVSS score of 9.8 reflects the high impact of complete confidentiality, integrity, and availability compromise, with no authentication or user interaction required.

04

What to do about it

no official fix yet

No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.

No fix documented in sources

05

Timeline

  1. Jun 9, 2026 · Jun 9, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 23, 2026 · 12d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
CVE-2026-47643: This vulnerability allows an attacker to control file names or paths o · Vulnary