Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0221 json

`event-listener` allows `!Send` tags to cross thread boundaries via `StackSlot`

published 3mo ago modified 3mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Affected versions of `event-listener` unconditionally implement `Send` and `Sync` for `StackSlot<'_, T>`, the stack-allocated listener type created by the `listener!` macro.

This allows a `!Send` tag type set via `Event::with_tag` to be moved to another thread and accessed via `StackSlot::wait`, causing a data race in safe code.

Patch / fix

  • crates.io event-listener 5.4.2

Is RUSTSEC-2026-0221 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io event-listener
>=5.1.0, <5.4.2
5.4.2

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.