Filtered by vendor Sonatype
Subscribe
Total
72 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2020-15869 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | 4.3 MEDIUM | 5.4 MEDIUM |
| Sonatype Nexus Repository Manager OSS/Pro versions before 3.25.1 allow XSS (issue 1 of 2). | |||||
| CVE-2020-15871 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | 6.8 MEDIUM | 8.8 HIGH |
| Sonatype Nexus Repository Manager OSS/Pro version before 3.25.1 allows Remote Code Execution. | |||||
| CVE-2020-15870 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | 4.3 MEDIUM | 6.1 MEDIUM |
| Sonatype Nexus Repository Manager OSS/Pro versions before 3.25.1 allow XSS (Issue 2 of 2). | |||||
| CVE-2026-77122 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 4.3 MEDIUM |
| An authorization flaw in the REST API repository details endpoint (GET /service/rest/v1/repositories/{repositoryName}) in Sonatype Nexus Repository 3 allowed an account holding read or browse permission on a group repository to retrieve metadata for member repositories on which it held no direct permission, by requesting the endpoint directly for the member repository name. For proxy repositories, the disclosed metadata includes the configured remote URL, which may reveal internal upstream hostnames. This includes the anonymous user if it has been granted this permission; whether the anonymous user holds this permission depends on the role and permission configuration of the specific installation. | |||||
| CVE-2026-77123 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 6.5 MEDIUM |
| Nexus Repository 3 contains a sensitive information disclosure vulnerability in the capability read API. An account holding the nexus:capabilities:read privilege can retrieve the plaintext shared secret configured on a webhook capability, which is intended to be masked from all API responses. This issue affects Nexus Repository 3 versions 3.2.0 through 3.95.x, and is fixed in version 3.96.0. | |||||
| CVE-2026-77124 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 7.2 HIGH |
| In affected versions of Nexus Repository 3, the script execution endpoint (POST /service/rest/v1/script/{name}/run) did not verify whether script execution had been administratively disabled. An account holding script-execution permission could continue to run previously-created scripts even after an administrator set nexus.scripts.allowCreation=false, undermining the expectation that this setting fully blocks script execution. | |||||
| CVE-2026-77125 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 7.1 HIGH |
| A vulnerability was identified in Sonatype Nexus Repository 3 in which two blobstore group management REST API endpoints did not correctly enforce the intended authorization check. A user granted only the nexus:blobstores:create permission could invoke these endpoints to convert an existing blobstore into a group blobstore, an action that should require the nexus:blobstores:update permission instead. This could result in unauthorized modification of blobstore configuration without administrator approval. The nexus:blobstores:create permission is a named permission that must be explicitly granted by an administrator; it is not held by default. | |||||
| CVE-2026-14644 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 7.2 HIGH |
| Nexus Repository 3 contained a privilege escalation vulnerability in the REST privileges API. An authenticated user with permission to manage privileges could, under certain role configurations, escalate their own access to full administrator by exploiting a type-confusion flaw in the privilege update endpoint. | |||||
| CVE-2026-17593 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 7.2 HIGH |
| An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against the set of registered realms. Because unrecognized entries were persisted and re-evaluated on every realm load via a legacy code path, this could result in unintended code executing inside the Nexus Repository process, and in some cases a persistent authentication lockout that was not visible through the administrative UI. | |||||
| CVE-2026-17594 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 4.9 MEDIUM |
| Nexus Repository 3 CE/Pro versions 3.0.0 through 3.94.x contain an incorrect authorization vulnerability (CWE-863) in the repository-creation user interface. An individual user account holding a delegated repository-admin privilege scoped to a specific repository format could create a repository of a different, unauthorized format, because authorization was checked against one request field while a separate, attacker-controlled field determined the repository format actually created. This does not affect the anonymous user, which cannot hold this privilege by default. Fixed in version 3.95.0. | |||||
| CVE-2026-17595 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 2.7 LOW |
| Nexus Repository 3 did not fully sandbox JEXL expressions used in Content Selectors. An account holding the nexus:selectors:create permission could construct an expression that read Java object properties not intended to be exposed to the expression engine, disclosing internal JVM class metadata such as class and classloader names. This issue does not permit method invocation, object construction, or arbitrary code execution. This has been fixed by restricting property access in the JEXL sandbox to the intended data types. | |||||
| CVE-2026-17596 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 6.1 MEDIUM |
| Nexus Repository 3 was found to be vulnerable to stored cross-site scripting (XSS). A user with the nexus:blobstores:create or nexus:blobstores:update permission could set a blob store name containing malicious script content, which would later execute in the browser of another user viewing system health-check status. This issue has been fixed in version 3.95.0. | |||||
| CVE-2026-17597 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-22 | N/A | 2.7 LOW |
| Nexus Repository 3 contains a Server-Side Request Forgery (SSRF) vulnerability in the email configuration verification feature. A user holding the nexus:settings:update permission could submit arbitrary host and port values to the email test/verification endpoint, causing the server to attempt outbound network connections to internal or otherwise restricted network addresses. Differences in the server's response could be used to infer whether internal hosts and ports are reachable. This issue affects Nexus Repository 3 CE/Pro versions up to and including 3.94.1, and is fixed in version 3.95.0. | |||||
| CVE-2026-3199 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-18 | N/A | 8.8 HIGH |
| A vulnerability in the task management component of Sonatype Nexus Repository versions 3.22.1 through 3.90.2 allows an authenticated attacker with task creation permissions to execute arbitrary code, bypassing the nexus.scripts.allowCreation security control. | |||||
| CVE-2026-3438 | 1 Sonatype | 1 Nexus Repository Manager | 2026-09-18 | N/A | 6.1 MEDIUM |
| A reflected cross-site scripting vulnerability exists in Sonatype Nexus Repository versions 3.0.0 through 3.90.2 that allows unauthenticated remote attackers to execute arbitrary JavaScript in a victim's browser through a specially crafted URL. Exploitation requires user interaction. | |||||
| CVE-2024-5764 | 1 Sonatype | 1 Nexus Repository Manager | 2026-06-17 | N/A | 6.5 MEDIUM |
| Use of Hard-coded Credentials vulnerability in Sonatype Nexus Repository has been discovered in the code responsible for encrypting any secrets stored in the Nexus Repository configuration database (SMTP or HTTP proxy credentials, user tokens, tokens, among others). The affected versions relied on a static hard-coded encryption passphrase. While it was possible for an administrator to define an alternate encryption passphrase, it could only be done at first boot and not updated. This issue affects Nexus Repository: from 3.0.0 through 3.72.0. | |||||
| CVE-2022-27907 | 1 Sonatype | 1 Nexus Repository Manager | 2026-06-17 | 4.0 MEDIUM | 4.3 MEDIUM |
| Sonatype Nexus Repository Manager 3.x before 3.38.0 allows SSRF. | |||||
| CVE-2021-43961 | 1 Sonatype | 1 Nexus Repository Manager | 2026-06-17 | 4.3 MEDIUM | 4.3 MEDIUM |
| Sonatype Nexus Repository Manager 3.36.0 allows HTML Injection. | |||||
| CVE-2021-43293 | 1 Sonatype | 1 Nexus Repository Manager | 2026-06-17 | 4.0 MEDIUM | 4.3 MEDIUM |
| Sonatype Nexus Repository Manager 3.x before 3.36.0 allows a remote authenticated attacker to potentially perform network enumeration via Server Side Request Forgery (SSRF). | |||||
| CVE-2021-42568 | 1 Sonatype | 1 Nexus Repository Manager | 2026-06-17 | 4.0 MEDIUM | 4.3 MEDIUM |
| Sonatype Nexus Repository Manager 3.x through 3.35.0 allows attackers to access the SSL Certificates Loading function via a low-privileged account. | |||||