Quick answers
- Is CVE-2026-110063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110063 being exploited in the wild.
- How severe is CVE-2026-110063?
- Critical severity, with a CVSS score of 10, published 22 October 2026.
- Which products and versions are affected?
- Microsoft VM Inspector for Azure Virtual Machines.
- Is there a fix for CVE-2026-110063?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-110063 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-110063?
- Check whether you run Microsoft VM Inspector for Azure Virtual Machines. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a symlink following (CWE-59) flaw in VM Inspector's file access logic that fails to properly validate or resolve symbolic links before performing file operations. An attacker can exploit this over the network to elevate privileges without requiring prior authentication or user interaction, gaining full system-level access to the affected virtual machine.
Affected products
- Microsoft VM Inspector for Azure Virtual Machines
Timeline
- 2026-10-22: disclosed