{"answers":{"affected":"1 open source package ship an affected version, including crossbeam-epoch.","exploited":"There is no known exploitation of RUSTSEC-2026-0204 in the wild and no public exploit code.","fix":"Upgrade crossbeam-epoch to 0.9.20 or later.","what":"RUSTSEC-2026-0204 is a vulnerability in crossbeam-epoch, published on 6 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0204 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0204 is a vulnerability in crossbeam-epoch, published on 6 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0204 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crossbeam-epoch (crates.io): affected from 0.9.0; fixed in 0.9.20\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-0204/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0204/index.md)","id":"RUSTSEC-2026-0204","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0204/index.md","name":"RUSTSEC-2026-0204","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust atomic library","requires_auth":"none","summary":"An attacker can cause a denial of service by triggering an invalid pointer dereference in the Display implementation for Atomic and Shared types.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.","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":true,"headline":"Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid","id":"RUSTSEC-2026-0204","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.9.20"],"introduced":["0.9.0"],"last_affected":[],"package":"crossbeam-epoch","purl":"pkg:cargo/crossbeam-epoch","source":"RUSTSEC-2026-0204"}],"products":null,"published":"2026-07-06","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":"An attacker can cause a denial of service by triggering an invalid pointer dereference in the Display implementation for Atomic and Shared types.","url":"https://insights.sbomify.com/RUSTSEC-2026-0204/"}