CVE-2019-16760
No exploitation reported by the sources we read.
- Published2019-09-30
- Fixed in0.27.0
- WeaknessCWE-16 · CWE-494
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Cargo prior to Rust 1.26.0 may download the wrong dependency if your package.toml file uses the `package` configuration key. Usage of the `package` key to rename dependencies in `Cargo.toml` is ignored in Rust 1.25.0 and prior. When Rust 1.25.0 and prior is used Cargo may download the wrong dependency, which could be squatted on crates.io to be a malicious package. This not only affects manifests that you write locally yourself, but also manifests published to crates.io. Rust 1.0.0 through Rust 1.25.0 is affected by this advisory because Cargo will ignore the `package` key in manifests. Rust 1.26.0 through Rust 1.30.0 are not affected and typically will emit an error because the `package` key is unstable. Rust 1.31.0 and after are not affected because Cargo understands the `package` key. Users of the affected versions are strongly encouraged to update their compiler to the latest available one. Preventing this issue from happening requires updating your compiler to be either Rust 1.26.0 or newer. There will be no point release for Rust versions prior to 1.26.0. Users of Rust 1.19.0 to Rust 1.25.0 can instead apply linked patches to mitigate the issue.
Timeline
dates in UTC- 2019-09-3022:15CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.27 | < 0.27.0 | 0.27.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.26 | < 1.26.0 | 1.26.0 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- cargoDebian:12all versions · fixed in 0.27.0-1
- rustCleanStartall versions · fixed in 1.26.0-r0
- rustAlpine:v3.24all versions · fixed in 1.26.0-r0and 1 other package
- rustAlpine:v3.23all versions · fixed in 1.26.0-r0
- rustAlpine:v3.22all versions · fixed in 1.26.0-r0
- rustAlpine:v3.21all versions · fixed in 1.26.0-r0
- rustAlpine:v3.20all versions · fixed in 1.26.0-r0
- rustAlpine:v3.19all versions · fixed in 1.26.0-r0
8 more package ranges on OSV.dev
Vendor advisories
- CVE-2019-16760 Red Hat Product Security
rust: privilege escaltion in cargo
Fix
- Update cargo to 0.27.0
Advisories and patches
- gist.github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.14.6known since 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-16known since 2026-10-23
- NVDweakness (CWE)CWE-494read 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2024-08-29
Identifiers
- EUVD-2022-3359same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-9f3p-wvj7-q82xsame flawGitHub Advisory Database · CC-BY-4.0
- GHSA-phjm-8x66-qw4rsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2019-09-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-9f3p-wvj7-q82x GHSA-phjm-8x66-qw4r
Frequently asked questions
What is CVE-2019-16760?
Is CVE-2019-16760 actively exploited?
What is the CVSS score for CVE-2019-16760?
Running cargo? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-9f3p-wvj7-q82x, GHSA-phjm-8x66-qw4r
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0