# CVE-2020-10199: Sonatype Nexus Repository Remote Code Execution

> Attackers can execute arbitrary code via Java Expression Language injection in Sonatype Nexus Repository.

- **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:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-g2f6-v5qh-h2mq

## What is CVE-2020-10199?

CVE-2020-10199 is a high-severity code injection vulnerability in n/a, published on 1 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sonatype Nexus Repository before 3.21.2 allows JavaEL Injection (issue 1 of 2).

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement)

## Which versions are affected by CVE-2020-10199?

2 open source packages ship an affected version, including org.sonatype.nexus:nexus-extdirect. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.sonatype.nexus:nexus-extdirect` | Maven | All versions | 3.21.2 |
| `org.sonatype.nexus:nexus-extdirect` | Maven | All versions | 3.21.2 |

Products: Sonatype Nexus.

## How do I fix CVE-2020-10199?

Upgrade org.sonatype.nexus:nexus-extdirect to 3.21.2 or later. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-10199 being exploited?

Yes. Attackers have exploited CVE-2020-10199 in the wild since at least 3 Nov 2021.

Public exploit code:

- CVE-2020-10199 Nexus <= 3.21.1 远程代码执行脚本(有回显) (github_poc): https://github.com/zhzyker/CVE-2020-10199_POC-EXP
- CVE-2020-10199、CVE-2020-10204、CVE-2020-11444 (github_poc): https://github.com/jas502n/CVE-2020-10199
- CVE-2020-10199 回显版本 (github_poc): https://github.com/aleenzz/CVE-2020-10199
- CVE-2020-10199、CVE-2020-10204漏洞一键检测工具，图形化界面。CVE-2020-10199 and CVE-2020-10204 Vul Tool with GUI. (github_poc): https://github.com/magicming200/CVE-2020-10199_CVE-2020-10204
- CVE-2020-10199 CVE-2020-10204 Python POC (github_poc): https://github.com/wsfengfan/CVE-2020-10199-10204
- Nexus Repository Manager Java EL Injection RCE (metasploit)

## Other vulnerabilities in n/a

- [CVE-2020-11444](https://insights.sbomify.com/CVE-2020-11444/): Missing authorization in n/a (high 8.8)
- [CVE-2014-9389](https://insights.sbomify.com/CVE-2014-9389/): Path traversal in n/a (high 7.5)
- [CVE-2014-2034](https://insights.sbomify.com/CVE-2014-2034/): Auth bypass in n/a (high 7.5)
- [CVE-2014-0792](https://insights.sbomify.com/CVE-2014-0792/): Deserialization in n/a (high 7.5)
- [CVE-2020-10204](https://insights.sbomify.com/CVE-2020-10204/): Remote Code Execution - JavaEL Injection (low privileged accounts) in Nexus Repository Manager (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10199 and fix it if it is affected.

What it is: CVE-2020-10199 is a high-severity code injection vulnerability in n/a, published on 1 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-10199 in the wild since at least 3 Nov 2021.

Affected packages and fixed versions:
- org.sonatype.nexus:nexus-extdirect (Maven): affected all versions; fixed in 3.21.2
- org.sonatype.nexus:nexus-extdirect (Maven): affected all versions; fixed in 3.21.2

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-2020-10199/ (Markdown: https://insights.sbomify.com/CVE-2020-10199/index.md)
```

## Sources

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

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