AIKIDO-2026-635394

TL;DR

Sticky (from the fragile package) validates access by comparing the current thread's ID against the ID recorded at creation, then reads the matching entry straight out of a global thread local registry. The registry does not track whether a thread's storage has since been torn down and reinitialized, so a handle created before teardown can still read or drop an entry that now belongs to a different, replaced registry generation, producing a stale or dangling access. A panic raised while that teardown runs aborts the whole process instead of failing safely. The fix adds a registry generation check and a teardown aware thread ID lookup so stale entries are rejected instead of accessed.