Question

A handful of users report that accounts they *logged out of* on a shared/public machine were later accessed by someone else — actions taken hours after they left. Your auth team confirms: logout clears the cookie in the browser but your API authorizes via a **stateless JWT** (24h expiry) and there's no server-side session/denylist, so a token captured before logout (e.g. via a shared browser's history, a proxy, or a copied cookie) keeps working until natural expiry. Login success rate, error rate, and traffic all look completely normal. How do you triage the scope, contain it, and fix it without logging out all 4M active sessions if you can avoid it?