How severe is CVE-2019-16530?

CVE-2019-16530 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-16530?

CVE-2019-16530 affects the following packages: org.sonatype.nexus:nexus-repository (Maven), org.sonatype.nexus:nexus-repository (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-16530?

Update org.sonatype.nexus:nexus-repository to 2.14.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16530 is resolved across your whole dependency graph.

How do I detect CVE-2019-16530 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sonatype.nexus:nexus-repository, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-16530 if there is no patch (or I can't update yet)?

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is CVE-2019-16530 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-16530 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-16530?

CVE-2019-16530 has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-16530?

CVE-2019-16530 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-16530 published, and has it been updated?

CVE-2019-16530 was published on October 21, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2019-16530 — nexus-repository

HIGH

CVE-2019-16530 is a high-severity (CVSS 7.2) Unrestricted File Upload vulnerability in org.sonatype.nexus:nexus-repository. A fix is available for org.sonatype.nexus:nexus-repository — see the affected versions and patch details below.

Unrestricted Upload of File with Dangerous Type in Sonatype Nexus Repository Manager

Also known asGHSA-hmjv-px3j-933c

Published

Oct 21, 2019

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.sonatype.nexus:nexus-repository☕org.sonatype.nexus:nexus-repository

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Sonatype Nexus Repository Manager 2.x before 2.14.15 and 3.x before 3.19, and IQ Server before 72, has remote code execution.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.sonatype.nexus:nexus-repository`	≥ 2.0.0&&< 2.14.15	2.14.15`org.sonatype.nexus:nexus-repository:2.14.15`
☕Maven	`org.sonatype.nexus:nexus-repository`	≥ 3.0.0&&< 3.19.0	3.19.0`org.sonatype.nexus:nexus-repository:3.19.0`

Affected Products

2 products · 3 configurations

Application

nexus iq serversonatype

≤ 72

range

Application

nexus repository managersonatype

≥ 3.0.0 && ≤ 3.18.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.sonatype.nexus:nexus-repository, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.sonatype.nexus:nexus-repository to 2.14.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16530 is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

Sonatype Nexus Repository Manager 2.x before 2.14.15 and 3.x before 3.19, and IQ Server before 72, has remote code execution.

O3 Security · Impact-Aware SCA

Is CVE-2019-16530 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-434Unrestricted File Upload

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 21, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-16530

GHSA-hmjv-px3j-933c

References

Advisoryissues.sonatype.org · ReleaseNote.jspa Advisorynvd.nist.gov · CVE 2019 16530 Fixsupport.sonatype.com

Related vulnerabilities

Also affects nexus-repository

This CVE is high severity, in line with the other 1 CVE affecting nexus-repository.

CVE-2021-40143

Same weakness: CWE-434

This CVE is high severity; 5 of 7 other CVEs with CWE-434 are rated as high or higher (top: high).

CVE-2026-61448CVE-2026-105862CVE-2026-105651CVE-2026-105649CVE-2026-105868CVE-2026-105679CVE-2026-105644Browse all CWE-434

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-16530 — nexus-repository

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-16530 in your dependencies?