Home › Intelligence › Brief
VULNERABILITY BRIEF🔴 Critical Vulnerability

Critical Access‑Control Flaw in Sonatype Nexus Repository Manager (CVE‑2019‑7238) Enables Remote Code Execution

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
HIGH
🏢
Affected
3 sector(s)
✅
Actions
5 recommended
📰
Source
nvd.nist.gov

Critical Access‑Control Flaw in Sonatype Nexus Repository Manager (CVE‑2019‑7238) Enables Remote Code Execution

What It Is

Sonatype Nexus Repository Manager versions < 3.15.0 contain an incorrect access‑control check that can be bypassed. An unauthenticated attacker can craft a request that triggers arbitrary code execution on the host running the repository service.

Exploitability

  • No public exploit code has been released, but the vulnerability is classified Critical (CVSS ≥ 9.0) and a proof‑of‑concept was demonstrated by the researcher who reported it. The flaw is exploitable over the network without authentication, making it a high‑risk vector for any exposed instance.

Affected Products

  • Sonatype Nexus Repository Manager (all editions) – versions prior to 3.15.0

Why It Matters for Compliance & Audit Readiness

The flaw directly impacts access‑control and vendor‑management controls that are core to continuous control monitoring frameworks (e.g., NIST CSF ID.AM‑1, ISO 27001 A.9). An unpatched repository can become a foothold for supply‑chain compromise, eroding the evidentiary trail required for audit readiness. Demonstrating timely patch management and validated access‑control configurations strengthens the defensible audit narrative around third‑party software risk and the integrity of build pipelines.

Recommended Actions

  • Inventory all Nexus Repository Manager instances and verify their version.
  • Patch any deployment running a version < 3.15.0 to the latest release.
  • Validate that repository‑level permissions align with the principle of least privilege; confirm that unauthenticated access is blocked.
  • Enable logging and alerting for anomalous HTTP requests to the repository service.
  • Document the remediation steps in your vendor‑risk register and retain logs as evidence of due diligence.

Source: https://nvd.nist.gov/vuln/detail/CVE-2019-7238

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2019-7238 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Answer one control objective. Answer ten frameworks.

The Verisq Common Framework is a spine of 84 control objectives that SOC 2, ISO 27001, NIST CSF, CMMC, HIPAA, PCI DSS, HITRUST, GDPR, ISO 42001 and NIST AI RMF map onto — each graded honestly. Satisfy an objective once and every framework that recognizes it lights up at its real strength.

See how the Verisq Common Framework works →