{"answers":{"affected":"1 open source package ship an affected version, including proc-macro1.","exploited":"There is no known exploitation of RUSTSEC-2026-0265 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0265 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0265 is a vulnerability in proc-macro1, published on 20 Aug 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-0265 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0265 is a vulnerability in proc-macro1, published on 20 Aug 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-0265 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- proc-macro1 (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-0265/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0265/index.md)","id":"RUSTSEC-2026-0265","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0265/index.md","name":"RUSTSEC-2026-0265","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 proc-macro1 was published to crates.io, allowing attackers to execute arbitrary code via its build script.","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":"It was reported `proc-macro1` contained a build script that would download a\nmalicious payload.\n\nThis crate had two versions, both published on 2026-08-20. The crate was\nremoved from crates.io and related user accounts were locked.\n\nThis crate was used as part of a malware campaign targeted at users of\n`arrayref`, which was downloaded 2,285 times before being removed; see\n[the `arrayref` advisory][arrayref-advisory] for more detail.\n\nThanks to the Research Team at Nextron Systems GmbH for reporting this to the\nRust security response working group, and thanks to Emily Albini for coordinating\nwith the crates.io and infra-admin teams.\n\n[arrayref-advisory]: https://rustsec.org/advisories/RUSTSEC-2026-0260.html","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":"`proc-macro1` was removed from crates.io due to malicious code","id":"RUSTSEC-2026-0265","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":"proc-macro1","purl":"pkg:cargo/proc-macro1","source":"RUSTSEC-2026-0265"}],"products":null,"published":"2026-08-20","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 proc-macro1 was published to crates.io, allowing attackers to execute arbitrary code via its build script.","url":"https://insights.sbomify.com/RUSTSEC-2026-0265/"}