CVE-2026-61422: Apache CloudStack · Server-Side Request Forgery (SSRF)
Affects Apache CloudStackSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache CloudStack | Affected
| Fixed in– |
Mavenorg.apache/cloudstackpkg:maven/org.apache/cloudstackOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache CloudStack to version 4.20.3.1 or 4.22.1.1 or later, where this vulnerability is fixed. No other mitigation is required as the vendor has provided an official fix.
Description
CVE-2026-61422 is an authenticated server-side request forgery (SSRF) vulnerability in Apache CloudStack affecting template and ISO registration. The vulnerability occurs because CloudStack makes a live HTTP HEAD/GET request to determine file size before validating the URL. However, URL validation is still performed before the actual download, reducing the risk of malicious template or ISO registration. The issue affects versions 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. Upgrading to versions 4.20.3.1 or 4.22.1.1 or later resolves the vulnerability.