{"answers":{"affected":"2 open source packages ship an affected version, including cargo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5223 in the wild and no public exploit code.","fix":"Upgrade cargo to 0.97.0 or later.","what":"CVE-2026-5223 is a medium-severity path traversal vulnerability in Rust Project Cargo, published on 25 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-5223 and fix it if it is affected.\n\nWhat it is: CVE-2026-5223 is a medium-severity path traversal vulnerability in Rust Project Cargo, published on 25 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-5223 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cargo (crates.io): affected all versions; fixed in 0.97.0\n- cargo (crates.io): affected all versions; fixed in 0.97.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5223/ (Markdown: https://insights.sbomify.com/CVE-2026-5223/index.md)","id":"CVE-2026-5223","markdown":"https://insights.sbomify.com/CVE-2026-5223/index.md","name":"CVE-2026-5223","record":{"aliases":["ALPINE-CVE-2026-5223","AZL-88272","AZL-88278","BELL-CVE-2026-5223","DEBIAN-CVE-2026-5223","GHSA-jq42-7mfv-hm57","MINI-g2wh-x4q6-q2w7","UBUNTU-CVE-2026-5223"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust package manager","requires_auth":"none","summary":"A malicious crate in a third-party registry can override another crate's source code via symlink handling, enabling supply chain attacks.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rust","cpe":[{"product":"cargo","vendor":"rust-lang"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"}],"description":"Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is **medium** for users of third-party registries. Users of crates.io are **not affected**, as crates.io forbids uploading crates containing any symlink.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Crates in third party registries can override the cached source of other crates","id":"CVE-2026-5223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Sensitive Data Exposure in Kriptek Crypto's Cryptosim","id":"CVE-2026-5224"},"packages":[{"ecosystem":"crates.io","fixed":["0.97.0"],"introduced":["0"],"last_affected":[],"package":"cargo","purl":null,"source":"GHSA-jq42-7mfv-hm57"},{"ecosystem":"crates.io","fixed":["0.97.0"],"introduced":["0"],"last_affected":[],"package":"cargo","purl":"pkg:cargo/cargo","source":"GHSA-jq42-7mfv-hm57"}],"prev":{"headline":"Cargo can be coerced to share credentials between registries","id":"CVE-2026-5222"},"products":["Cargo"],"published":"2026-05-25","related":[{"cvss_score":5.3,"headline":"Cargo did not verify SSH host keys","id":"CVE-2022-46176","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":4.8,"headline":"Extracting malicious crates can fill the file system","id":"CVE-2022-36114","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":4.6,"headline":"Extracting malicious crates can corrupt arbitrary files","id":"CVE-2022-36113","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":2.3,"headline":"Cargo can be coerced to share credentials between registries","id":"CVE-2026-5222","kev_date_added":null,"published":"2026-05-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["Rust Project"]},"summary":"A malicious crate in a third-party registry can override another crate's source code via symlink handling, enabling supply chain attacks.","url":"https://insights.sbomify.com/CVE-2026-5223/"}