CVE-2026-113372
Received Received - Intake

Sonatype Nexus Repository 3 YUM Repository Private Key Exposure

Vulnerability report for CVE-2026-113372, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: Sonatype

Description

Sonatype Nexus Repository 3 returns the private signing key of a YUM proxy or group repository to an account that holds only the read privilege for administering that repository. The account does not need the privilege to edit the repository. A party that holds the key can sign repository metadata as that repository.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-04
Last Modified
2026-11-04
Generated
2026-11-04
AI Q&A
2026-11-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Sonatype Nexus Repository 3 3.93.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-113372 is a vulnerability in Sonatype Nexus Repository 3 where the private signing key of a YUM proxy or group repository is exposed to accounts with only read privileges for administering that repository. This occurs even though the account lacks edit privileges, and the repository uses the key to sign its metadata.

Detection Guidance

To detect this vulnerability, check if any accounts with only read privileges for YUM proxy or group repositories have access to private signing keys. Review Nexus Repository role assignments and repository configurations for exposed keys. Use Nexus Repository logs to identify unauthorized access attempts to signing keys.

Impact Analysis

An attacker with read access to the repository could obtain the private signing key and use it to sign malicious repository metadata. This could allow the attacker to distribute compromised packages to users of the repository, leading to potential code execution or data breaches on systems that trust the repository.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles or HIPAA's security requirements for protected health information. Organizations may face compliance penalties if the exposure results in a data breach.

Mitigation Strategies
  • Upgrade to Sonatype Nexus Repository 3.98.0 or later to patch the vulnerability.
  • Restrict repository administration read privileges to fully trusted accounts only.
  • Rotate any exposed private signing keys and update client trust configurations.
  • Limit network access to the Nexus Repository web interface and REST API.
  • Review and audit role and group mappings for unnecessary privileges.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-113372. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...