CVE-2020-11753 Nexus Repository 3 - Improper Access Controls - 2020-04-16

Sonatype Nexus Repository 3 Security Advisory

Date: April 16th, 2020

Affected Versions:  Nexus Repository 3 OSS/Pro versions 3.21.1 and 3.22.0

Fixed in Version:  Nexus Repository OSS/Pro version 3.22.1

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


Improper access controls have been discovered in Nexus Repository 3.

A privileged user can craft requests in such a manner that scripting tasks can be created, updated or executed without use of the user interface or REST API.  We have mitigated the issue by implementing the necessary access controls. 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 are highly recommending all instances of Nexus Repository be upgraded to version 3.22.1 or later. The latest version of Nexus Repository 3.x can be downloaded from:

For detailed information on upgrade compatibility, please see:


Sonatype thanks shadowsock5 for responsibly reporting the identified issues and working with us as we addressed them.


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 create, update or execute scripts outside the typical use of the user interface or REST API.


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

A: The user must have privileges to perform the scripting actions.  The ability to perform scripting actions must be enabled if on a 3.22.0 version.


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.