CVE-2026-59657: Apache CloudStack · Cleartext Storage of Sensitive Information
Affects Apache CloudStackSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 4.20.3.1 : patch Apache CloudStack soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 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 18 Nov 2026.
What to do
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 Apache CloudStack to version 4.20.3.1 or 4.22.1.1 or later to remediate this vulnerability. These versions contain the official fix for the cleartext storage issue. No other mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-59657 is a high-severity vulnerability in Apache CloudStack that involves cleartext storage of sensitive information in the AsyncJob database storage. This affects versions from 4.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. The vulnerability allows sensitive data to be stored without encryption, potentially exposing it to unauthorized access. The issue is fixed in versions 4.20.3.1 and 4.22.1.1 or later.