CVE-2020-15871 Nexus Repository Manager 3 - Remote Code Execution - 2020-07-29

Sonatype Nexus Repository Manager 3 Security Advisory

Date:  July 29th, 2020

Affected Versions:  All previous Nexus Repository Manager 3 OSS/Pro versions up to and including 3.25.0

Fixed in Version:  Nexus Repository Manager OSS/Pro version 3.25.1

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


A remote code execution vulnerability (CVE-2020-15871) has been discovered in Nexus Repository Manager 3.

A user with the right permissions can run arbitrary code as the user running the Nexus Repository Manager server. Alternatively, an attacker could trick a user with the right permissions into running arbitrary code as the user running the Nexus Repository Manager server. We have fixed the issue so that the remote code execution is no longer possible. 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. However, we strongly encourage all users of Nexus Repository Manager 3 to immediately take the steps outlined in this advisory.

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

For detailed information on upgrade, please see:


Sonatype thanks codeplutos @ antfin non-attack security lab for responsibly reporting the identified issue and working with us as we addressed it.


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:  An attacker can run arbitrary code on the system as the user running Nexus Repository Manager.


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

A: An attacker must have the right permissions on the server or trick another user that does have the right permissions.


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 Nexus Repository Manager is an open source project with over 150,000 active server installations, 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.