CVE-2020-10199 Nexus Repository 3 - Remote Code Execution - 2020-03-31

Sonatype Nexus Security Advisory

Date:  March 31, 2020

Affected Versions:  All previous Nexus Repository 3.x OSS/Pro versions up to and including 3.21.1

Fixed in Version:  Nexus Repository OSS/Pro version 3.21.2

Risk: Critical - 9.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H)


A Remote Code Execution vulnerability has been discovered in Nexus Repository requiring immediate action. The vulnerability allows for an attacker with any type of account on Nexus Repository to execute arbitrary code by crafting a malicious request to Nexus Repository We have mitigated the issue by adjusting the configuration of third-party library that allowed for this attack. This advisory provides the pertinent information needed to properly address this vulnerability, along with the details on how to reach us if you have any further questions or concerns.

This vulnerability was identified by an external researcher and has been verified by our security team. We are not aware of any active exploits taking advantage of this issue.

The identified vulnerability can allow for the user to evaluate any code they send on the system, that the user running the server has privileges to.


We are highly recommending all affected instances of Nexus Repository be upgraded to 3.21.2 or later. The latest version can be downloaded from:

For detailed information on upgrade, please see:

Upgrading Nexus Repository Manager 3.1.0 and Newer


This issue was discovered and reported by Github Security Lab team member @pwntester (Alvaro Muñoz).


If you run into any problems, or have any questions/concerns, please contact us  by filing a ticket at

Frequently Asked Questions:

Q:  What is the risk associated with this vulnerability?

A:  Nexus Repository can be compromised, allowing an attacker to use the flaw to execute code outside the scope of the Nexus Repository server.


Q: What preconditions must be met in order to be vulnerable?

A: An attacker must have network access to the Nexus Repository instance, as well as a user account access to the Repository Manager to send the malicious request.


Q: Are there implications associated with this advisory itself?

A: Disclosure unfortunately means bad actors may try to take advantage.  While we have initially limited the information to the minimum details necessary for users to affect an appropriate fix, this merely slows down a would be attacker.  As such, we are advising all organizations utilizing Nexus Repository Manager to immediately assess their individual impact and take appropriate action in response.


Q:  Where can I obtain more information associated with the vulnerability?

A:  At this time, and in the interest of best protecting our user community, we are limiting the information released to that absolutely required in order to assess impact and affect remediation. Please contact support for more information.


Q:  Why is Sonatype making this information available?

A:  This is part of a responsible disclosure process.  Given NXRM is an open source project with widespread usage, notifying the user base will invariably lead to broad dissemination.  We are taking a concerted and proactive approach in our outreach activities and an effort to achieve the most rapid remediation possible.

Have more questions? Submit a request


Article is closed for comments.