# CVE-2021-1626: Code injection in Mulesoft

> Attackers can execute arbitrary code on MuleSoft runtime environments, affecting both cloud and on-premise deployments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mjff-hx99-hm9w

## What is CVE-2021-1626?

CVE-2021-1626 is a critical code injection vulnerability in Mulesoft, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MuleSoft is aware of a Remote Code Execution vulnerability affecting certain versions of a Mule runtime component that may affect both CloudHub and on-premise customers. Versions affected: Mule 4.1.x and 4.2.x runtime released before February 2, 2021.

## Which versions are affected by CVE-2021-1626?

It affects 1 product.


Products: Salesforce Mule.

## How do I fix CVE-2021-1626?

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

## Is CVE-2021-1626 being exploited?

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

## Other vulnerabilities in Mulesoft

- [CVE-2021-1627](https://insights.sbomify.com/CVE-2021-1627/): Server-side request forgery in Mulesoft (critical 9.8)
- [CVE-2021-1628](https://insights.sbomify.com/CVE-2021-1628/): XML external entity in Mulesoft (critical 9.8)
- [CVE-2021-1630](https://insights.sbomify.com/CVE-2021-1630/): XML external entity in Mulesoft (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1626 and fix it if it is affected.

What it is: CVE-2021-1626 is a critical code injection vulnerability in Mulesoft, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-1626 in the wild and no public exploit code.

Affected product: Mulesoft. 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-2021-1626/ (Markdown: https://insights.sbomify.com/CVE-2021-1626/index.md)
```

## Sources

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

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