Code Injection
Source GCVE Database
Not known to be exploited · CVSS 4.7 Medium : upgrade to 4.22.0 or 4.20.2 when convenient.
Data as of 19 Nov 2026, 02:21 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 4.7 |
|---|
- Patch
- Available – fixed in 4.22.0, 4.20.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 27 Nov 2025
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
Upgrade Apache CloudStack to 4.22.0 or 4.20.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache CloudStack | 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.2 or 4.22.0, where the vulnerability is fixed. The fix includes a new global configuration flag, js.interpretation.enabled, which administrators can use to control JavaScript expression interpretation in the affected APIs, mitigating the code injection risk. No other specific mitigations are indicated.
Description
Apache CloudStack versions from 4.18.0 before 4.20.2 and from 4.21.0 before 4.22.0 contain a code injection vulnerability in several admin-only APIs. The affected APIs include quotaTariffCreate, quotaTariffUpdate, createSecondaryStorageSelector, updateSecondaryStorageSelector, updateHost, and updateStorage. The vulnerability arises from improper control over the generation of code, allowing potential injection of malicious JavaScript expressions. The issue is addressed by introducing a global configuration flag, js.interpretation.enabled, which lets administrators control JavaScript interpretation in these APIs. Users are advised to upgrade to versions 4.20.2 or 4.22.0 where the fix is implemented.