Security readout for executives and security teams
Plain-English summary
This is a critical Microsoft Azure Stack Edge vulnerability that could let an unauthenticated network attacker run code. The issue involves external control of a filename or path. Organizations using Azure Stack Edge 2.2.0 should treat it as urgent because confidentiality, integrity, and availability impacts are rated high.
Executive priority
Prioritize within the critical patch window for any Azure Stack Edge 2.2.0 deployment, especially if network reachable. The risk is severe, but the source bundle does not prove active exploitation.
Technical view
CVE-2026-47643 is a CWE-73 path or filename control flaw in Microsoft Azure Stack Edge 2.2.0. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Microsoft lists it as remote code execution with an official remediation available.
Likely exposure
Exposure is most likely where Azure Stack Edge version 2.2.0 is deployed and reachable over a network. The bundle does not identify other affected versions, deployment modes, or required service exposure.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. CVSS exploit maturity is listed as unproven, so exploitation should not be claimed from this bundle alone.
Researcher notes
The public bundle gives severity, CWE, affected product/version, and vendor advisory, but limited technical detail. Avoid assuming additional versions, exploit paths, or compensating controls beyond Microsoft guidance.
Mitigation direction
- Review Microsoft MSRC guidance for CVE-2026-47643 immediately.
- Apply the Microsoft-supported update or remediation for affected Azure Stack Edge systems.
- Inventory Azure Stack Edge appliances and confirm whether version 2.2.0 is present.
- Limit network reachability to affected appliances until remediation is verified.
- Monitor Microsoft guidance for any scope or exploitation updates.
Validation and detection
- Check Azure Stack Edge versions against the affected version listed in the advisory.
- Confirm the Microsoft remediation is installed on all affected appliances.
- Verify affected appliances are not unnecessarily reachable from untrusted networks.
- Review security monitoring for unusual access to affected Azure Stack Edge systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-47643 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C3.95.9microsoftVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Azure Stack Edge Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.