llamaCVEVulnerability Intelligence
/
Advisory · GitHub · crates.io · cargo

GHSA-P688-R7JV-FM6F

Cargo can be coerced to share credentials between registries

Parche disponible
Descargar PNG JSON
CVSS
—
low
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -29 d de la divulgación
Exposición145 dDesde la divulgación, 26 jun 2026, 4:47 p. m.
Detección143 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 0.97.0
Monitoreo
Detectada
28 may 26
26 jun 26
17 nov 26
19 nov 26
28 may 26
11 jul 26
24 ago 26
6 oct 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 0.97.0 cargo · -29 d desde divulgación
Divulgación Publicada GHSA-P688-R7JV-FM6F divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

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

Versiones

Rangos afectados

Afectada Corregida Última
cargo< 0.97.0
0.97.0
0.100.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
crates.iocargo
Corregida 0.97.0 -29 d 0.100.0 no afectada
Versiones corregidas0.97.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-5222
Otrahttps://github.com/rust-lang/cargo/security/advisories/GHSA-p688-r7jv-fm6f
Otrahttps://github.com/rust-lang/cargo/pull/17031
Otrahttps://blog.rust-lang.org/2026/05/25/cve-2026-5222
Otrahttps://github.com/rust-lang/cargo
Otrahttps://groups.google.com/g/rustlang-security-announcements/c/SfUxOiIdY5s

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.