CVE-2026-61398: Improper Encoding or Escaping of Output vulnerability in Apache CloudStack's UI while using Instance
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.22.1.1 or 4.20.3.1 as a priority.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.22.1.1, 4.20.3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 19 Nov 2026.
What to do
Upgrade org.apache.cloudstack/cloudstack to 4.22.1.1 or 4.20.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache CloudStack | Affected
| Fixed in– |
Mavenorg.apache.cloudstack/cloudstackpkg:maven/org.apache.cloudstack/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 affected Apache CloudStack instances to version 4.20.3.1, 4.22.1.1, or later, where the vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.
Description
An improper encoding or escaping of output vulnerability exists in the Apache CloudStack UI related to the Instance Reset Password functionality. This affects versions from 4.15.1.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. The issue is resolved in versions 4.20.3.1 and 4.22.1.1 or later.