Quick answers
- Is CVE-2026-58279 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58279 being exploited in the wild.
- How severe is CVE-2026-58279?
- Medium severity, with a CVSS score of 6.5, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Azure CycleCloud >= 1.0.0, < 8.9.1.
- Is there a fix for CVE-2026-58279?
- 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-58279 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-58279?
- Check whether you run Microsoft Azure CycleCloud at an affected version. 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
A missing authorization vulnerability (CWE-862) exists in Microsoft Azure CycleCloud versions prior to 8.9.1. The flaw allows a remote attacker with low-privileged user credentials to bypass authorization checks over the network. By exploiting this root cause, the attacker can achieve an elevation of privilege, specifically impacting the integrity of the system (CVSS I:H). The attack does not require user interaction or high complexity. Microsoft has addressed this issue in Azure CycleCloud version 8.9.1.
Affected products
- Microsoft Azure CycleCloud >= 1.0.0, < 8.9.1
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory