CVE-2026-5222: Cargo Remote Code Execution Vulnerability

LOW
Advisory Identifier: GHSA-p688-r7jv-fm6f
CWE-647
Published
Advisory Summary

CVE-2026-5222 is a LOW remote code execution vulnerability (CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions) affecting Cargo libraries in the crates.io ecosystem. The issue involves cargo can be coerced to share credentials between registries. Remediation is available by upgrading affected packages to version 0.97.0.

CVE-2026-5222 at a Glance

CVE Identifier CVE-2026-5222
GHSA Identifier GHSA-p688-r7jv-fm6f
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions
Affected Product Cargo
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-5222

To remediate this vulnerability, upgrade all affected Cargo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cargo fixed: 0.97.0
Upgrade cargo to 0.97.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for cargo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-5222, inspect your project dependencies for Cargo:

inspect dependencies for cargo

Analyze the terminal output to locate any version of Cargo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.97.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions, where the product defines policy namespaces and makes authorization decisions based on the assumption that a url is canonical. this can allow a non-canonical url to bypass the authorization. In Cargo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The Rust Security Response Team was notified that Cargo incorrectly normalized the URLs of third-party registries using the [sparse index protocol][1]. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. This vulnerability is tracked as CVE-2026-5222. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack. ## Overview Originally Cargo only supported storing a registry's index within git repositories. Most git hosting solutions allow accessing a git repository with or without the `.git` suffix, so Cargo mirrored this behavior when normalizing registry URLs. This allowed credentials for `https://example.com/index` to be used for `https://example.com/index.git`. This normalization was unintentionally applied to the new sparse indexes too. Sparse indexes can be hosted on any HTTPS server, which treat URLs ending with `.git` as different URLs than those without the suffix. If the following conditions apply: * `https://example.com/index` is a sparse index. * `https://example.com/index` allows crates to depend on crates from any other registry. * The attacker is able to publish crates on `https://example.com/index`. * The attacker is able to upload arbitrary files to `https://example.com/index.git`. ...the attacker could configure `https://example.com/index.git` to be a Cargo sparse registry requiring authentication for downloads, and with a download URL pointing to a server recording any credentials set to it. When the attacker then publishes a crate `foo` to `https://example.com/index` depending on a crate `bar` from `https://example.com/index.git`, and tricks the victim into downloading `foo`, Cargo will think the two registries share the same credential and send the victim's Cargo token to the malicious registry. ## Mitigations Rust 1.96, to be released on May 28th, 2026, will update Cargo to only strip the `.git` suffix from registry URLs using the git protocol. No mitigations are available for users of older versions of Cargo. ## Affected versions All versions of Cargo shipped between Rust 1.68 (the stabilization of sparse registries) and 1.96 are affected. ## Acknowledgements Cargo would like to thank Christos Papakonstantinou for reporting this issue according to the [Rust security policy][2]. Cargo also wants to thank the members of the Rust project who helped address the vulnerability: Arlo Siemens for developing the fix; Weihang Lo, Eric Huss and Emily Albini for reviewing the fix; Emily Albini for writing this advisory; Emily Albini, Josh Stone and Manish Goregaokar for coordinating the disclosure. [1]: https://doc.rust-lang.org/cargo/reference/registries.html#registry-protocols [2]: https://rust-lang.org/policies/security

CVE-2026-5222 Affected Cargo Versions

1 component(s)
Fixed Versions:
0.97.0
Product / Package Ecosystem Affected Versions Fixed Version
cargo
crates.io
< 0.97.0
0.97.0

References

Frequently Asked Questions

What is CVE-2026-5222?
CVE-2026-5222 is a security vulnerability in Cargo involving Cargo can be coerced to share credentials between registries under CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions.
Which Cargo versions are affected?
Affected versions include releases prior to 0.97.0 across affected packages: cargo.
What version fixes CVE-2026-5222?
Upgrading to 0.97.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is cargo affected?
Yes, cargo is affected in releases prior to 0.97.0. Upgrade your dependency to 0.97.0 or later.
What CWE is associated with CVE-2026-5222?
CVE-2026-5222 is classified under CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions (The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization.).
How can I check crates.io dependencies for CVE-2026-5222?
Run the dependency tree command: 'inspect dependencies for cargo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p688-r7jv-fm6f",
  "modified" : "2026-06-26T21:47:54Z",
  "published" : "2026-06-26T21:47:54Z",
  "aliases" : [ "CVE-2026-5222" ],
  "summary" : "Cargo can be coerced to share credentials between registries",
  "details" : "The Rust Security Response Team was notified that Cargo incorrectly normalized the URLs of third-party registries using the [sparse index protocol][1]. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry.\n\nThis vulnerability is tracked as CVE-2026-5222. The severity of the vulnerability is **low**, due to the extremely niche requirements needed to achieve the attack.\n\n## Overview\n\nOriginally Cargo only supported storing a registry's index within git repositories. Most git hosting solutions allow accessing a git repository with or without the `.git` suffix, so Cargo mirrored this behavior when normalizing registry URLs. This allowed credentials for `https://example.com/index` to be used for `https://example.com/index.git`.\n\nThis normalization was unintentionally applied to the new sparse indexes too. Sparse indexes can be hosted on any HTTPS server, which treat URLs ending with `.git` as different URLs than those without the suffix.\n\nIf the following conditions apply:\n\n* `https://example.com/index` is a sparse index.\n* `https://example.com/index` allows crates to depend on crates from any other registry.\n* The attacker is able to publish crates on `https://example.com/index`.\n* The attacker is able to upload arbitrary files to `https://example.com/index.git`.\n\n...the attacker could configure `https://example.com/index.git` to be a Cargo sparse registry requiring authentication for downloads, and with a download URL pointing to a server recording any credentials set to it.\n\nWhen the attacker then publishes a crate `foo` to `https://example.com/index` depending on a crate `bar` from `https://example.com/index.git`, and tricks the victim into downloading `foo`,  Cargo will think the two registries share the same credential and send the victim's Cargo token to the malicious registry.\n\n## Mitigations\n\nRust 1.96, to be released on May 28th, 2026, will update Cargo to only strip the `.git` suffix from registry URLs using the git protocol. No mitigations are available for users of older versions of Cargo.\n\n## Affected versions\n\nAll versions of Cargo shipped between Rust 1.68 (the stabilization of sparse registries) and 1.96 are affected.\n\n## Acknowledgements\n\nCargo would like to thank Christos Papakonstantinou for reporting this issue according to the [Rust security policy][2].\n\nCargo also wants to thank the members of the Rust project who helped address the vulnerability: Arlo Siemens for developing the fix; Weihang Lo, Eric Huss and Emily Albini for reviewing the fix; Emily Albini for writing this advisory; Emily Albini, Josh Stone and Manish Goregaokar for coordinating the disclosure.\n\n[1]: https://doc.rust-lang.org/cargo/reference/registries.html#registry-protocols\n[2]: https://rust-lang.org/policies/security",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "cargo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.97.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rust-lang/cargo/security/advisories/GHSA-p688-r7jv-fm6f"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-5222"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rust-lang/cargo/pull/17031"
  }, {
    "type" : "WEB",
    "url" : "https://blog.rust-lang.org/2026/05/25/cve-2026-5222"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rust-lang/cargo"
  }, {
    "type" : "WEB",
    "url" : "https://groups.google.com/g/rustlang-security-announcements/c/SfUxOiIdY5s"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-647" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T21:47:54Z",
    "nvd_published_at" : "2026-05-25T10:16:15Z"
  }
}