{"answers":{"affected":"1 open source package ship an affected version, including logtrace.","exploited":"There is no known exploitation of RUSTSEC-2026-0081 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0081 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0081 is a vulnerability in logtrace, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0081 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0081 is a vulnerability in logtrace, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0081 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- logtrace (crates.io): affected from 0.0.0-0; no fix listed\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/RUSTSEC-2026-0081/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0081/index.md)","id":"RUSTSEC-2026-0081","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0081/index.md","name":"RUSTSEC-2026-0081","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crate","requires_auth":"none","summary":"A malicious Rust crate named logtrace was published to crates.io, potentially allowing remote code execution via a Remote Access Trojan.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`logtrace` appeared to be downloading a RAT.\n\nThe malicious crate had 2 versions published on 2026-04-01 that had a total of 30 downloads. There\nwere no crates depending on this crate on crates.io.\n\nThanks to [Socket.dev](https://socket.dev/) for detecting and reporting this to the crates.io team!","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"`logtrace` was removed from crates.io for malicious code","id":"RUSTSEC-2026-0081","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"logtrace","purl":"pkg:cargo/logtrace","source":"RUSTSEC-2026-0081"}],"products":null,"published":"2026-04-05","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious Rust crate named logtrace was published to crates.io, potentially allowing remote code execution via a Remote Access Trojan.","url":"https://insights.sbomify.com/RUSTSEC-2026-0081/"}