Nexus Repository 3 - Insufficiently Protected Credentials in YUM Repository Signing Key
Affects Sonatype Nexus Repository 3 CE/Pro versions from 3.93.0 up to, but not including, 3.98.0, only where a YUM proxy or group repository has a signing key configured. Fixed in 3.98.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.98.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The instance has a YUM proxy or group repository with a signing key configured. Affected Nexus Repository 3 CE/Pro versions from 3.93.0 up to, but not including, 3.98.0.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-113372 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Nexus Repository 3; fixed in 3.98.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.98.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Sonatype Nexus Repository 3 returns the private signing key of YUM proxy and group repositories to a remote attacker who logs in with an account that has only the read privilege for administering that repository. An attacker who holds the key can sign repository metadata as that repository.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
The instance has a YUM proxy or group repository with a signing key configured. Affected Nexus Repository 3 CE/Pro versions from 3.93.0 up to, but not including, 3.98.0.Upgrade to a fixed version: 3.98.0.
Workaround: Grant the YUM repository administration read privilege only to fully trusted accounts and restrict access to the Nexus web interface and REST API to trusted networks.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Sonatype Nexus Repository 3
From 3.93.0 · fixed in 3.98.0
Evidence 2
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113372
Is CVE-2026-113372 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets an attacker read the private signing key of a YUM proxy or group repository. Anyone holding that key can sign repository metadata as that repository.Source: support.sonatype.com
Which versions are affected by CVE-2026-113372?
Nexus Repository 3: from 3.93.0 before 3.98.0.Source: cve.now feed data
Am I affected, and how do I check?
Nexus Repository 3 CE/Pro versions from 3.93.0 up to, but not including, 3.98.0 are in scope, and only when a YUM proxy or group repository has a signing key configured. To check, look at the version shown in the instance's administration area and review whether any YUM repository has a signing key set.Source: support.sonatype.com
How do I fix CVE-2026-113372?
Upgrade to Sonatype Nexus Repository 3 CE/Pro version 3.98.0 or later.Source: support.sonatype.com