Nexus Repository 3
Monthly
Script execution enforcement failure in Sonatype Nexus Repository 3 allows privileged authenticated users to invoke pre-existing Groovy scripts via POST /service/rest/v1/script/{name}/run even after administrators explicitly set nexus.scripts.allowCreation=false to disable the scripting subsystem. The execution endpoint did not consult the administrative flag, meaning a hardening action administrators believed fully blocked script activity was silently ineffective against execution of pre-existing scripts. A vendor-released patch is available in Nexus Repository 3.96.0; no active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified.
Incorrect authorization in Sonatype Nexus Repository 3 allows a low-privileged user holding the `nexus:blobstores:create` permission to invoke two blobstore group management REST API endpoints that should instead require `nexus:blobstores:update`. By calling these endpoints, the user can convert any existing blobstore into a group blobstore - a structural configuration change - without administrator approval. No public exploit has been identified, but the issue is self-reported by Sonatype and a patch is available in version 3.96.0.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated user holding privilege-management rights to elevate their own access to full administrator by exploiting a type-confusion flaw (CWE-843) in the REST privilege update endpoint. Exploitation is constrained to specific role configurations, but the network-accessible attack surface and high confidentiality and integrity impact (VC:H/VI:H per the CVSS 4.0 vector) make this a meaningful insider or compromised-account risk in enterprise DevOps environments. A vendor-released patch is available in the Nexus Repository 3.95.0 release; no public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect authorization in the Nexus Repository 3 CE/Pro repository-creation UI allows an authenticated user with a format-scoped delegated repository-admin privilege to create repositories in unauthorized formats - bypassing the intended scope boundary. Affected are all releases from 3.0.0 through 3.94.x; version 3.95.0 resolves the flaw. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, but the integrity impact is high given that unauthorized repository types could be introduced into a managed artifact store, potentially tainting software supply chain pipelines.
Insufficient session expiration in Sonatype Nexus Repository 3 allows a previously-authenticated user to retain full repository access after their account is deleted, deactivated, or their password is changed. Any user holding an active session at the moment of an administrative revocation event can continue reading, modifying, or deleting repository content until that session naturally times out - bypassing the intended access control action. No public exploit has been identified and this is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 reflects the high-impact triad of confidentiality, integrity, and availability against network-accessible repositories once the prerequisite session exists.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated low-privileged user - who holds the 'update privilege definitions' permission - to silently elevate themselves to full administrative access by editing wildcard privilege definitions already scoped to their own role. No additional authorization check, role reassignment, or administrator approval is required for this escalation. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.9 and the complete confidentiality, integrity, and availability impact - including lateral impact on downstream systems - indicate high real-world risk for any organization using Nexus Repository 3 as a software supply chain hub.
Remote code execution in Sonatype Nexus Repository 3 is achievable by any user holding the nx-datastores-update permission, who can exploit an insufficiently restricted HikariCP connection-pool property passthrough in the DataStore configuration API to inject arbitrary SQL via the connectionInitSql property. On the default H2 embedded database backend - common in non-production and smaller deployments - H2's ability to invoke Java methods from SQL allows this injection to escalate to OS-level command execution as the Nexus process user. No public exploit has been identified at time of analysis, but the H2-to-RCE escalation path is a well-understood Java ecosystem technique that lowers the practical skill bar significantly.
Authorization bypass in Sonatype Nexus Repository 3's component upload API lets an account holding only read/browse privileges on a Swift, Terraform, or Conda hosted repository push arbitrary artifacts, defeating the intended write-permission check (CWE-862). The flaw affects the specific upload paths for these three formats and enables unauthorized artifact publishing that can poison downstream builds. No public exploit identified at time of analysis; Sonatype has shipped a fix in release 3.94.0.
Targeted repository denial-of-service in Sonatype Nexus Repository 3 allows any authenticated user holding deploy privileges to permanently disable component browsing on a specific hosted Maven repository. Uploading a crafted POM file with an oversized metadata field (CWE-770) corrupts the repository's internal data such that subsequent listing and browse operations fail indefinitely until an administrator repairs the underlying record. Impact is confined to the single targeted repository; the broader Nexus instance and all other repositories remain unaffected. No public exploit has been identified at time of analysis.
Improper authorization in Sonatype Nexus Repository 3 exposes repository metadata to users who lack direct permissions on those repositories. An account holding read or browse access on a group repository can directly query the REST API endpoint `GET /service/rest/v1/repositories/{repositoryName}` for any member repository by name, bypassing the access control checks that normally restrict visibility. For proxy-type member repositories, the disclosed metadata includes the configured remote URL, potentially revealing internal upstream hostnames or artifact mirror addresses that operators intend to keep private. No public exploit has been identified at time of analysis, and the issue is patched in version 3.96.0.
The webhook shared secret stored in Nexus Repository 3's capability configuration is returned unmasked via the capability read API, exposing a sensitive HMAC credential to any account holding the nexus:capabilities:read privilege. Affected versions span 3.2.0 through 3.95.x - a broad exposure window stretching back to an early release - with a confirmed fix in version 3.96.0 published by Sonatype. No public exploit or active exploitation has been identified, but a leaked webhook secret enables downstream abuse including forging authenticated webhook payloads or validating intercepted outbound events targeting CI/CD or pipeline endpoints.
JEXL expression sandbox bypass in Sonatype Nexus Repository 3's Content Selector feature allows authenticated users holding the nexus:selectors:create permission to traverse Java object properties outside the intended sandbox scope, disclosing internal JVM metadata such as class and classloader names. The vendor description explicitly confirms this does not permit method invocation, object construction, or code execution - making the 'RCE' intelligence tag a misclassification. Fixed in version 3.95.0; no public exploit or active exploitation has been identified at time of analysis.
Stored XSS in Sonatype Nexus Repository 3 enables an authenticated user holding blob store management permissions to inject arbitrary JavaScript into a blob store name, which later executes in the browser of any user who views the system health-check status page. The CVSS 4.0 vector's SC:H/SI:H scores underscore that the subsequent-system impact is high - an attacker-controlled script running in a victim's session can exfiltrate credentials or perform privileged actions on their behalf. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; Sonatype has released a fix in version 3.95.0.
Scheduled task configuration overwrite in Sonatype Nexus Repository 3 enables a low-privileged authenticated user - holding permission to create at least one scheduled task type - to corrupt the configuration of an unrelated existing task via mass assignment against the administrative UI. By injecting internal configuration keys into user-supplied task property values, the attacker causes the system to redirect its write operation onto a pre-existing task rather than creating a new one, disrupting or manipulating that task's behavior. No public exploit or active exploitation has been identified; vendor-released patch 3.95.0 resolves the issue.
Unverified password change in Sonatype Nexus Repository 3 allows any account holding the nexus:* permission to overwrite the administrator password by invoking an onboarding-phase endpoint that remains accessible after initial setup is complete. The endpoint enforces access using only the presence of a local onboarding artifact rather than a proper lifecycle state check, enabling a privileged-but-non-admin account to hijack the administrator credential without invalidating existing administrator sessions. No public exploit has been identified at time of analysis and Sonatype has released a fix in version 3.95.0.
The email configuration verification endpoint in Sonatype Nexus Repository 3 (CE and Pro editions through 3.94.1) allows authenticated users holding the nexus:settings:update permission to submit arbitrary host and port values, causing the server to probe internal or restricted network addresses via Server-Side Request Forgery. Differences in server responses - connection timing, error codes, and success signals - act as a side channel revealing which internal hosts and ports are reachable from the Nexus server, enabling internal network enumeration. No public exploit has been identified at time of analysis, and vendor-released patch version 3.95.0 resolves the issue.
SSRF protections in Sonatype Nexus Repository 3 are bypassed when proxy repository upstream servers return HTTP redirects, allowing those redirects to target internal network addresses or cloud metadata endpoints such as AWS IMDSv1. Any user with read access to an affected proxy repository - including anonymous users if anonymous access is enabled - can receive responses from internal infrastructure, potentially leaking cloud IAM credentials or other sensitive internal data. No public exploit or CISA KEV listing has been identified at time of analysis, but the condition relies on attacker-controlled or compromised upstream servers, making this a credible supply-chain-adjacent threat in enterprises relying on external upstream repositories.
Server-Side Request Forgery in Sonatype Nexus Repository 3 allows any holder of the Capability Administration permission to redirect the server's outbound HTTP requests to arbitrary internal network addresses by supplying a crafted URL in the Webhook Global capability configuration, enabling probing of internal infrastructure. The vulnerability is patched in version 3.94.0 per Sonatype's release notes. No public exploit code exists and the vulnerability is not in CISA KEV, but risk escalates materially on instances where the anonymous role has been granted the Capability Administration permission, as this exposes the SSRF to unauthenticated actors without any configuration changes beyond that role assignment.
Script execution enforcement failure in Sonatype Nexus Repository 3 allows privileged authenticated users to invoke pre-existing Groovy scripts via POST /service/rest/v1/script/{name}/run even after administrators explicitly set nexus.scripts.allowCreation=false to disable the scripting subsystem. The execution endpoint did not consult the administrative flag, meaning a hardening action administrators believed fully blocked script activity was silently ineffective against execution of pre-existing scripts. A vendor-released patch is available in Nexus Repository 3.96.0; no active exploitation has been confirmed in CISA KEV and no public proof-of-concept has been identified.
Incorrect authorization in Sonatype Nexus Repository 3 allows a low-privileged user holding the `nexus:blobstores:create` permission to invoke two blobstore group management REST API endpoints that should instead require `nexus:blobstores:update`. By calling these endpoints, the user can convert any existing blobstore into a group blobstore - a structural configuration change - without administrator approval. No public exploit has been identified, but the issue is self-reported by Sonatype and a patch is available in version 3.96.0.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated user holding privilege-management rights to elevate their own access to full administrator by exploiting a type-confusion flaw (CWE-843) in the REST privilege update endpoint. Exploitation is constrained to specific role configurations, but the network-accessible attack surface and high confidentiality and integrity impact (VC:H/VI:H per the CVSS 4.0 vector) make this a meaningful insider or compromised-account risk in enterprise DevOps environments. A vendor-released patch is available in the Nexus Repository 3.95.0 release; no public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect authorization in the Nexus Repository 3 CE/Pro repository-creation UI allows an authenticated user with a format-scoped delegated repository-admin privilege to create repositories in unauthorized formats - bypassing the intended scope boundary. Affected are all releases from 3.0.0 through 3.94.x; version 3.95.0 resolves the flaw. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, but the integrity impact is high given that unauthorized repository types could be introduced into a managed artifact store, potentially tainting software supply chain pipelines.
Insufficient session expiration in Sonatype Nexus Repository 3 allows a previously-authenticated user to retain full repository access after their account is deleted, deactivated, or their password is changed. Any user holding an active session at the moment of an administrative revocation event can continue reading, modifying, or deleting repository content until that session naturally times out - bypassing the intended access control action. No public exploit has been identified and this is not listed in CISA KEV, but the CVSS 4.0 score of 8.7 reflects the high-impact triad of confidentiality, integrity, and availability against network-accessible repositories once the prerequisite session exists.
Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated low-privileged user - who holds the 'update privilege definitions' permission - to silently elevate themselves to full administrative access by editing wildcard privilege definitions already scoped to their own role. No additional authorization check, role reassignment, or administrator approval is required for this escalation. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.9 and the complete confidentiality, integrity, and availability impact - including lateral impact on downstream systems - indicate high real-world risk for any organization using Nexus Repository 3 as a software supply chain hub.
Remote code execution in Sonatype Nexus Repository 3 is achievable by any user holding the nx-datastores-update permission, who can exploit an insufficiently restricted HikariCP connection-pool property passthrough in the DataStore configuration API to inject arbitrary SQL via the connectionInitSql property. On the default H2 embedded database backend - common in non-production and smaller deployments - H2's ability to invoke Java methods from SQL allows this injection to escalate to OS-level command execution as the Nexus process user. No public exploit has been identified at time of analysis, but the H2-to-RCE escalation path is a well-understood Java ecosystem technique that lowers the practical skill bar significantly.
Authorization bypass in Sonatype Nexus Repository 3's component upload API lets an account holding only read/browse privileges on a Swift, Terraform, or Conda hosted repository push arbitrary artifacts, defeating the intended write-permission check (CWE-862). The flaw affects the specific upload paths for these three formats and enables unauthorized artifact publishing that can poison downstream builds. No public exploit identified at time of analysis; Sonatype has shipped a fix in release 3.94.0.
Targeted repository denial-of-service in Sonatype Nexus Repository 3 allows any authenticated user holding deploy privileges to permanently disable component browsing on a specific hosted Maven repository. Uploading a crafted POM file with an oversized metadata field (CWE-770) corrupts the repository's internal data such that subsequent listing and browse operations fail indefinitely until an administrator repairs the underlying record. Impact is confined to the single targeted repository; the broader Nexus instance and all other repositories remain unaffected. No public exploit has been identified at time of analysis.
Improper authorization in Sonatype Nexus Repository 3 exposes repository metadata to users who lack direct permissions on those repositories. An account holding read or browse access on a group repository can directly query the REST API endpoint `GET /service/rest/v1/repositories/{repositoryName}` for any member repository by name, bypassing the access control checks that normally restrict visibility. For proxy-type member repositories, the disclosed metadata includes the configured remote URL, potentially revealing internal upstream hostnames or artifact mirror addresses that operators intend to keep private. No public exploit has been identified at time of analysis, and the issue is patched in version 3.96.0.
The webhook shared secret stored in Nexus Repository 3's capability configuration is returned unmasked via the capability read API, exposing a sensitive HMAC credential to any account holding the nexus:capabilities:read privilege. Affected versions span 3.2.0 through 3.95.x - a broad exposure window stretching back to an early release - with a confirmed fix in version 3.96.0 published by Sonatype. No public exploit or active exploitation has been identified, but a leaked webhook secret enables downstream abuse including forging authenticated webhook payloads or validating intercepted outbound events targeting CI/CD or pipeline endpoints.
JEXL expression sandbox bypass in Sonatype Nexus Repository 3's Content Selector feature allows authenticated users holding the nexus:selectors:create permission to traverse Java object properties outside the intended sandbox scope, disclosing internal JVM metadata such as class and classloader names. The vendor description explicitly confirms this does not permit method invocation, object construction, or code execution - making the 'RCE' intelligence tag a misclassification. Fixed in version 3.95.0; no public exploit or active exploitation has been identified at time of analysis.
Stored XSS in Sonatype Nexus Repository 3 enables an authenticated user holding blob store management permissions to inject arbitrary JavaScript into a blob store name, which later executes in the browser of any user who views the system health-check status page. The CVSS 4.0 vector's SC:H/SI:H scores underscore that the subsequent-system impact is high - an attacker-controlled script running in a victim's session can exfiltrate credentials or perform privileged actions on their behalf. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; Sonatype has released a fix in version 3.95.0.
Scheduled task configuration overwrite in Sonatype Nexus Repository 3 enables a low-privileged authenticated user - holding permission to create at least one scheduled task type - to corrupt the configuration of an unrelated existing task via mass assignment against the administrative UI. By injecting internal configuration keys into user-supplied task property values, the attacker causes the system to redirect its write operation onto a pre-existing task rather than creating a new one, disrupting or manipulating that task's behavior. No public exploit or active exploitation has been identified; vendor-released patch 3.95.0 resolves the issue.
Unverified password change in Sonatype Nexus Repository 3 allows any account holding the nexus:* permission to overwrite the administrator password by invoking an onboarding-phase endpoint that remains accessible after initial setup is complete. The endpoint enforces access using only the presence of a local onboarding artifact rather than a proper lifecycle state check, enabling a privileged-but-non-admin account to hijack the administrator credential without invalidating existing administrator sessions. No public exploit has been identified at time of analysis and Sonatype has released a fix in version 3.95.0.
The email configuration verification endpoint in Sonatype Nexus Repository 3 (CE and Pro editions through 3.94.1) allows authenticated users holding the nexus:settings:update permission to submit arbitrary host and port values, causing the server to probe internal or restricted network addresses via Server-Side Request Forgery. Differences in server responses - connection timing, error codes, and success signals - act as a side channel revealing which internal hosts and ports are reachable from the Nexus server, enabling internal network enumeration. No public exploit has been identified at time of analysis, and vendor-released patch version 3.95.0 resolves the issue.
SSRF protections in Sonatype Nexus Repository 3 are bypassed when proxy repository upstream servers return HTTP redirects, allowing those redirects to target internal network addresses or cloud metadata endpoints such as AWS IMDSv1. Any user with read access to an affected proxy repository - including anonymous users if anonymous access is enabled - can receive responses from internal infrastructure, potentially leaking cloud IAM credentials or other sensitive internal data. No public exploit or CISA KEV listing has been identified at time of analysis, but the condition relies on attacker-controlled or compromised upstream servers, making this a credible supply-chain-adjacent threat in enterprises relying on external upstream repositories.
Server-Side Request Forgery in Sonatype Nexus Repository 3 allows any holder of the Capability Administration permission to redirect the server's outbound HTTP requests to arbitrary internal network addresses by supplying a crafted URL in the Webhook Global capability configuration, enabling probing of internal infrastructure. The vulnerability is patched in version 3.94.0 per Sonatype's release notes. No public exploit code exists and the vulnerability is not in CISA KEV, but risk escalates materially on instances where the anonymous role has been granted the Capability Administration permission, as this exposes the SSRF to unauthenticated actors without any configuration changes beyond that role assignment.