Oh, one more thought since I didn&#x27;t really address state leak. Let&#x27;s pretend we&#x27;re in a C-like language that is not memory safe. You&#x27;re not reseeding and you don&#x27;t have forward secrecy. Someone finds a buffer overflow and manages to get your CSPRNG state. Now they can recover the sequence of randomness you&#x27;ve handed out in the past (maybe they&#x27;re access tokens, for instance). It&#x27;s not a trivial attack, but it&#x27;s plausible.<p>If you don&#x27;t like the buffer overflow example, let&#x27;s make it a misconfigured website that leaks the state in an error message or stack trace served to an end user.