{"answers":{"affected":"1 open source package ship an affected version, including event-listener.","exploited":"There is no known exploitation of RUSTSEC-2026-0221 in the wild and no public exploit code.","fix":"Upgrade event-listener to 5.4.2 or later.","what":"RUSTSEC-2026-0221 is a vulnerability in event-listener, published on 13 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0221 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0221 is a vulnerability in event-listener, published on 13 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0221 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- event-listener (crates.io): affected from 5.1.0; fixed in 5.4.2\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-0221/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0221/index.md)","id":"RUSTSEC-2026-0221","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0221/index.md","name":"RUSTSEC-2026-0221","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust event-listener library","requires_auth":"none","summary":"The event-listener library allows unsafe thread boundary crossings for non-Send types, causing data races in safe code.","user_interaction":"not_required","vuln_class":"race_condition"},"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 `event-listener` unconditionally implement `Send` and\n`Sync` for `StackSlot\u003c'_, T\u003e`, the stack-allocated listener type created\nby the `listener!` macro.\n\nThis allows a `!Send` tag type set via `Event::with_tag` to be moved to\nanother thread and accessed via `StackSlot::wait`, causing a data race in safe\ncode.","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":"`event-listener` allows `!Send` tags to cross thread boundaries via `StackSlot`","id":"RUSTSEC-2026-0221","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["5.4.2"],"introduced":["5.1.0"],"last_affected":[],"package":"event-listener","purl":"pkg:cargo/event-listener","source":"RUSTSEC-2026-0221"}],"products":null,"published":"2026-07-13","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":"The event-listener library allows unsafe thread boundary crossings for non-Send types, causing data races in safe code.","url":"https://insights.sbomify.com/RUSTSEC-2026-0221/"}