Skip to content
Fencer Vulns
critical 9.9

CVE-2024-43602 json

Azure CycleCloud Remote Code Execution Vulnerability

published 2024-11-12 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-40353

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Azure CycleCloud Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Azure CycleCloud 8.6.5
  • Microsoft Azure CycleCloud 8.0.0 8.6.5
  • Microsoft Azure CycleCloud 8.0.1 8.6.5
  • Microsoft Azure CycleCloud 8.6.0 8.6.5
  • Microsoft Azure CycleCloud 8.0.2 8.6.5
  • Microsoft Azure CycleCloud 8.1.0 8.6.5
  • Microsoft Azure CycleCloud 8.2.0 8.6.5
  • Microsoft Azure CycleCloud 8.2.1 8.6.5
  • Microsoft Azure CycleCloud 8.2.2 8.6.5
  • Microsoft Azure CycleCloud 8.4.1 8.6.5
  • Microsoft Azure CycleCloud 8.1.1 8.6.5
  • Microsoft Azure CycleCloud 8.4.2 8.6.5
  • Microsoft Azure CycleCloud 8.4.0 8.6.5
  • Microsoft Azure CycleCloud 8.5.0 8.6.5
  • Microsoft Azure CycleCloud 8.3.0 8.6.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
23 mo ago

Exploit prediction

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Microsoft Azure CycleCloud
  • Microsoft Azure CycleCloud 8.0.0
  • Microsoft Azure CycleCloud 8.0.1
  • Microsoft Azure CycleCloud 8.6.0
  • Microsoft Azure CycleCloud 8.0.2
  • Microsoft Azure CycleCloud 8.1.0
  • Microsoft Azure CycleCloud 8.2.0
  • Microsoft Azure CycleCloud 8.2.1
  • Microsoft Azure CycleCloud 8.2.2
  • Microsoft Azure CycleCloud 8.4.1
  • Microsoft Azure CycleCloud 8.1.1
  • Microsoft Azure CycleCloud 8.4.2
  • Microsoft Azure CycleCloud 8.4.0
  • Microsoft Azure CycleCloud 8.5.0
  • Microsoft Azure CycleCloud 8.3.0

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.