CVE-2019-15893 Nexus Repository 2 - Remote Code Execution - 2019-09-03

Sonatype Nexus Security Advisory

Date:  October 15th, 2019

Affected Versions:  All previous Nexus Repository OSS/Pro versions up to and including 2.14.15

Fixed in Version:  Nexus Repository OSS/Pro version 2.14.16

Risk: Critical - 9.1 (CVSS:3.0/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 2, requiring immediate action. The vulnerability allows for an attacker with administrative access to Nexus Repository to create repositories that can grant access to read/execute system data outside the scope of Nexus Repository. We have mitigated the issue by not allowing Nexus Repository 2 to do this unless explicitly requested by system administrators. 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 2 to immediately take the steps outlined in this advisory.

The identified vulnerability can allow for the server to execute anything on the system, that the user running the server has privileges to. We are highly recommending all instances of Nexus Repository 2 be upgraded to 2.14.16 or later.

For detailed information on upgrade compatibility, please see:


Sonatype thanks Christian Håland @ Binary Security for responsibly reporting the identified issue.


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 2 storage can be compromised, allowing an attacker to use the flaw to read or execute files 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 administrative access to the Nexus Repository to apply the required storage configurations.


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 2 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 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.