CVE-2026-113368: Nexus Repository 3 - Group Repository Member Authorization Bypass
Sonatype Nexus Repository 3 does not check that a user account is authorized to access a repository before the repository is added as a member of a group repository. A user account that has signed in with valid credentials and holds the add or edit privilege on a group repository can add a repository that the account cannot read or browse, and then read the content of that repository through the group. The anonymous user can only do this if an administrator has explicitly granted it that privilege.
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user with the add or edit privilege on a group repository can exploit it. Anonymous access is only relevant if an administrator has explicitly granted the anonymous user that privilege.
What access can an attacker gain through a vulnerable group repository?
The attacker can add a repository they are not authorized to read or browse as a member of a group repository, then read that repository's content through the group.
How can I determine whether my deployment is exposed?
Review which accounts have add or edit privileges on group repositories and whether those accounts lack read or browse authorization for repositories that could be added to those groups. Also check whether the anonymous user has been explicitly granted group-repository add or edit privileges.