Secuno
ENNL
Book demo

CVE-2026-69555

Microsoft Azure Arc broken access control

10.0 CRITICALEPSS 0.80%
  1. Published20 Aug 2026

Description

Incorrect authorization in Azure Arc allows an unauthorized attacker to elevate privileges over a network.

CVSS 3.1 breakdown

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

Affected products

Microsoft Azure Arcall versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-163018.5
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before…
CVE-2026-1095598.7
EdgeEver Desktop 1.6.26 through 1.112.0 contains a navigation allowlist bypass that…
CVE-2026-773669.9
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian…
CVE-2026-1039038.8
An incorrect authorization vulnerability in the WinBox authentication flow of MikroTik…
CVE-2026-1087468.8
Vearch 3.5.2 through 3.5.9 contains an incorrect authorization vulnerability in…
CVE-2026-816499.1
The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper…

Frequently asked

Is CVE-2026-69555 being actively exploited?

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

How severe is CVE-2026-69555?

CVE-2026-69555 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.80% probability of exploitation.

Which products are affected by CVE-2026-69555?

Affected products include Microsoft Azure Arc.

How do I fix CVE-2026-69555?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-69555 against the real software inventory on every managed device, as each hourly inventory arrives. 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.