* Someone inspecting the page with developer tools
* Logs that accidentally (or intentionally) contain the cookie
* A corporate (or government) firewall that intercepts plaintext traffic
* Someone with temporary physical access to the machine that can use the TPM or secure enclave to decrypt the cookie jar.
* A mistake in the cookie configuration and/or DNS leads to the cookie getting sent to the wrong server.
This would protect against those scenarios.