Secuno
ENNL
Book demo

CVE-2026-47643

Microsoft Azure Stack Edge path traversal

9.8 CRITICALEPSS 0.97%
  1. Published9 Jun 2026

Description

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

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Microsoft Azure Stack Edge< 3.3.2604.3097

Remediation

Fixed in
Microsoft Azure Stack Edge≥ 3.3.2604.3097

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-599768.1
ConvertX is a self-hosted file conversion service. Prior to 0.18.0, the ImageMagick…
CVE-2026-1058658.1
Payload is a free and open source headless content management system. In versions…
CVE-2026-976628.2
An argument injection issue in the diff scan operation in AWS security-agent-mcp-server…
CVE-2026-1032559.0
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1…
CVE-2026-159838.1
The Super Forms – Drag & Drop Form Builder plugin for WordPress is vulnerable to…
CVE-2026-192538.7
The Cache Enabler WordPress plugin before 1.8.17 does not validate a URL before using…

Frequently asked

Is CVE-2026-47643 being actively exploited?

CVE-2026-47643 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.97%.

How severe is CVE-2026-47643?

CVE-2026-47643 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.97% probability of exploitation.

Which products are affected by CVE-2026-47643?

Affected products include Microsoft Azure Stack Edge.

How do I fix CVE-2026-47643?

Upgrade affected software to a fixed version, for example Microsoft Azure Stack Edge 3.3.2604.3097 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-47643 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.