Developer Finds Safari MCP Server Bug That Silently Mints Invalid Tab Tokens
A developer discovered a critical bug in their Safari MCP server where browser tab ownership tokens became invalid after a daemon restart. The flaw stemmed from a cached browser-session epoch in the extension's background worker that was never refreshed from storage, causing newly minted tokens to carry a stale identifier. When the worker eventually cold-started, it discarded all stored records tied to the outdated epoch, instantly invalidating every token created during the restart window. Affected tabs became permanently stranded — commands were refused and the tokens could not be rotated or recovered from the client side. The bug went undetected because six separate safety checks all passed silently, with only the final rehydration path actually comparing the epoch against storage.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in