CVE-2026-113372
Nexus Repository 3 - Insufficiently Protected Credentials in YUM Repository Signing Key
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.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: SonatypeAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Nexus Repository 3 Sonatype |
≥ 3.93.0; < 3.98.0 (affected, semver)
Other versions: unaffected |
CNA: Sonatype |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 7.1 high |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N | CNA: Sonatype |
| 4.0 / 7.1 high |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | NVD: 103e4ec9-0a87-450b-af77-479448ddef11 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.htmlCNA: Sonatype · patch
- https://support.sonatype.com/hc/en-us/articles/56612283547539/CNA: Sonatype · vendor-advisory
- https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html103e4ec9-0a87-450b-af77-479448ddef11
- https://support.sonatype.com/hc/en-us/articles/56612283547539/103e4ec9-0a87-450b-af77-479448ddef11
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.