CVE-2026-59655: Apache CloudStack · Information Exposure
Affects Apache CloudStackSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 4.22.1.1 or 4.20.3.1 soon.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 49% 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: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 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 installations to versions 4.20.3.1 or 4.22.1.1 or later, where this vulnerability has been fixed. No other mitigation or temporary workaround is indicated in the available data.
Description
CVE-2026-59655 is a vulnerability in Apache CloudStack's OAuth authentication plugin that allows exposure of sensitive information to unauthorized actors when listing OAuth providers. This affects versions from 4.19.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. The issue is fixed in versions 4.20.3.1 and 4.22.1.1 or later.