How severe is CVE-2026-65816?

CVE-2026-65816 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-65816 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-65816?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-65816 published?

CVE-2026-65816 was published on 2026-08-20 and last updated on 2026-08-22.

CVE-2026-65816

CVE-2026-65816 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-706.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
EPSS exploit prediction: 1% (43rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-706
Published: 2026-08-20
Last modified: 2026-08-22

Description

Use of incorrectly-resolved name or reference in Azure Arc allows an unauthorized attacker to elevate privileges over a network.

Frequently asked questions

What is CVE-2026-65816?: Use of incorrectly-resolved name or reference in Azure Arc allows an unauthorized attacker to elevate privileges over a network.
How severe is CVE-2026-65816?: CVE-2026-65816 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-65816 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-65816?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-65816 published?: CVE-2026-65816 was published on 2026-08-20 and last updated on 2026-08-22.

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-65816

Other CWE-706 vulnerabilities

CVE-2025-65474 — Critical (CVSS 9.8): An arbitrary file rename vulnerability in the /admin/manager.php component of EasyImages 2.0 v2.8.6 and below allows…
CVE-2024-35198 — Critical (CVSS 9.8): TorchServe is a flexible and easy-to-use tool for serving and scaling PyTorch models in production. TorchServe 's check…
CVE-2023-31814 — Critical (CVSS 9.8): D-Link DIR-300 firmware <=REVA1.06 and <=REVB2.06 is vulnerable to File inclusion via /model/__lang_msg.php.
CVE-2022-30258 — Critical (CVSS 9.8): An issue was discovered in Technitium DNS Server through 8.0.2 that allows variant V2 of unintended domain name…
CVE-2022-30257 — Critical (CVSS 9.8): An issue was discovered in Technitium DNS Server through 8.0.2 that allows variant V1 of unintended domain name…
CVE-2021-40539 — Critical (CVSS 9.8): Zoho ManageEngine ADSelfService Plus version 6113 and prior is vulnerable to REST API authentication bypass with…

Browse all CWE-706 vulnerabilities →