CVE-2026-57969
Missing auth in Azure CycleCloud enables remote privilege escalation to admin.
Is CVE-2026-57969 being exploited?
Not confirmed. CVE-2026-57969 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-57969?
CVE-2026-57969 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57969?
Yes. A fix has been recorded for CVE-2026-57969. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57969 affect?
CVE-2026-57969 affects Azure CycleCloud, CycleCloud API, Azure HPC clusters. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57969?
Apply vendor patch when available; restrict CycleCloud network access and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Missing authentication on a CycleCloud function allows remote privilege escalation to admin, enabling cluster takeover, job manipulation, and data access.
Immediate action required
- affected>= 1.0.0 and < 8.9.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.