# CVE-2026-47643: Azure Stack Edge Remote Code Execution Vulnerability

> An unauthorized attacker can execute code over the network via external control of file names or paths in Azure Stack Edge.

- **Severity:** Critical 9.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-hcqg-8f35-jw4g

## What is CVE-2026-47643?

CVE-2026-47643 is a critical path traversal vulnerability in Microsoft Azure Stack Edge, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-47643?

It affects 1 product.


Products: Microsoft Azure Stack Edge.

## How do I fix CVE-2026-47643?

No fix has been published for CVE-2026-47643 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47643 being exploited?

There is no known exploitation of CVE-2026-47643 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Azure Stack Edge

- [CVE-2026-41098](https://insights.sbomify.com/CVE-2026-41098/): Azure Stack Edge Spoofing Vulnerability (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47643 and fix it if it is affected.

What it is: CVE-2026-47643 is a critical path traversal vulnerability in Microsoft Azure Stack Edge, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47643 in the wild and no public exploit code.

Affected product: Microsoft Azure Stack Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47643/ (Markdown: https://insights.sbomify.com/CVE-2026-47643/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47643
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47643
- OSV: https://osv.dev/vulnerability/CVE-2026-47643

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47643/
Summaries are generated and may contain mistakes; the official description above is the record.