# CVE-2026-50112: Apache CloudStack: RCE and SSRF in direct download, metalink and NFS templates

> Authenticated tenants can trigger SSRF and execute arbitrary root commands on KVM hypervisors via malicious metalink templates.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 22 Aug 2026
- **Also known as:** GHSA-qh8m-g3r9-6vh2

## What is CVE-2026-50112?

CVE-2026-50112 is a high-severity server-side request forgery vulnerability in Apache Cloudstack, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SSRF via Metalink Mirror URL Resolution:

An authenticated tenant can register a template pointing to an attacker-controlled metalink file containing internal targets. The Secondary Storage VM will retrieve the data and persist it as a template file, which can later be downloaded through normal APIs.

RCE on KVM hypervisor via NFS, Metalink files with/without Direct Downloads:

An authenticated CloudStack tenant holding the default User role can execute arbitrary shell commands as root on the KVM hypervisor host that runs other tenants' VMs. This is cross-tenant root on the underlying compute, reachable via the public CloudStack API.

When a User registers a VM template with directDownload=true and a URL pointing to a .metalink file, the management server fetches the metalink XML and dispatches download to the KVM agent. Inner URLs inside the metalink XML are never re-validated against the scheme allowlist.

These issues affect Apache CloudStack: from 4.14.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0.

Users are recommended to upgrade to version 4.20.3.1 or 4.22.1.1 or later, which fixes the issue.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-50112?

It affects 1 product.


Products: Apache Cloudstack.

## How do I fix CVE-2026-50112?

No fix has been published for CVE-2026-50112 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-50112 being exploited?

There is no known exploitation of CVE-2026-50112 in the wild and no public exploit code.

## Other vulnerabilities in Apache Cloudstack

- [CVE-2012-4501](https://insights.sbomify.com/CVE-2012-4501/): Missing authorization in n/a (critical 10.0)
- [CVE-2024-38346](https://insights.sbomify.com/CVE-2024-38346/): Apache CloudStack: Unauthenticated cluster service port leads to remote execution (critical 9.8)
- [CVE-2024-39864](https://insights.sbomify.com/CVE-2024-39864/): Apache CloudStack: Integration API service uses dynamic port when disabled (critical 9.8)
- [CVE-2024-29006](https://insights.sbomify.com/CVE-2024-29006/): Apache CloudStack: x-forwarded-for HTTP header parsed by default (critical 9.8)
- [CVE-2022-35741](https://insights.sbomify.com/CVE-2022-35741/): Apache CloudStack SAML Single Sign-On XXE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50112 and fix it if it is affected.

What it is: CVE-2026-50112 is a high-severity server-side request forgery vulnerability in Apache Cloudstack, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50112 in the wild and no public exploit code.

Affected product: Apache Cloudstack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50112/ (Markdown: https://insights.sbomify.com/CVE-2026-50112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50112
- OSV: https://osv.dev/vulnerability/CVE-2026-50112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50112/
Summaries are generated and may contain mistakes; the official description above is the record.