CVE-2026-113372Sonatype Nexus Repository 3 insufficiently protected credentials
CVE-2026-113372 is a insufficiently protected credentials in Sonatype Nexus Repository 3, rated high (7.1 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Undergoing Analysis
What it is
Credentials are stored or sent in a way others can recover.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.21% chance of exploitation activity in the next 30 days, higher than 12% of scored CVEs.
What to do
- Upgrade Sonatype Nexus Repository 3 to 3.98.0 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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 this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.
Questions to answer about your own systems
- Where does Sonatype Nexus Repository 3 run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.