Skip to main content
No exploitation reportedFix available

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?

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
  1. 2019-09-3022:15CVE publishedNVD

Versions per branch

OSV · NVD
cargo
BranchAffectedFixed in
0.27< 0.27.00.27.0
Rust-lang rust
BranchAffectedFixed in
1.26< 1.26.01.26.0

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

Full record on NVD

Fix

  1. Update cargo to 0.27.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
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

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

Frequently asked questions

What is CVE-2019-16760?

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.

Is CVE-2019-16760 actively exploited?

Active exploitation of CVE-2019-16760 has not been confirmed. Its EPSS score was 1.3% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-16760?

CVE-2019-16760 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

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

Sources for this record