Distribution advisory
This page covers CVE-2026-5222 as tracked by Ubuntu, for the package cargo. No fixed version has been recorded for this distribution yet.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: High — total loss, or loss the attacker controls.
- Integrity impact: None.
- Availability impact: None.
Weakness class
UBUNTU-CVE-2026-5222 is classified as 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.
Affected software
UBUNTU-CVE-2026-5222 is recorded against 19 packages.
- cargo
- rustc
- rustc-1.62
- rustc-1.74
- rustc-1.76
- rustc-1.77
- rustc-1.78
- rustc-1.79
- rustc-1.80
- rustc-1.81
- rustc-1.82
- rustc-1.83
- rustc-1.84
- rustc-1.85
- rustc-1.88
- rustc-1.89
- rustc-1.91
- rustc-1.92
- rustc-1.93
Timeline and source
Published on 25 May 2026 and last revised on 3 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
blog.rust-lang.org (Report)
github.com (Report)
groups.google.com (Report)
Other advisories for this package
cargo has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-647: Use of Non-Canonical URL Paths for Authorization Decisions) in other software:
