basicsecurity.net
Proof, not just disclosure.
Threats / Sonatype / CVE-2019-7238
CVE-2019-7238 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Sonatype Nexus Repository Manager vulnerability

Sonatype Nexus Repository Manager before 3.15.0 contains an incorrect access control vulnerability enabling remote code execution.

Verdict

Today item — known-exploited.

An access control flaw in Nexus Repository Manager allows unauthenticated or unauthorized attackers to execute arbitrary code on affected systems. The high EPSS score and active exploitation in the wild indicate immediate risk to unpatched deployments.

CISA KEV Yes · 2021-12-103EPSS 0.76526 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
857 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.76526 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Sonatype, Nexus Repository Manager. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I identify that Nexus Repository Manager enforces insufficient access controls on a critical endpoint or function.
Business
Attackers gain unauthorized access to the artifact repository, a central component of the software supply chain.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the access control bypass to execute arbitrary code on the Nexus server.
Business
The organization loses control of its repository infrastructure and all stored artifacts become compromised.
3

Lateral reach — past segmentation narrative 3

Attacker
I inject malicious code into stored artifacts or modify build pipelines connected to the repository.
Business
Downstream applications and customers receive compromised software, creating widespread supply chain contamination.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 857 reported-exploitation source(s)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.