Breaking the Patch: Perplexity’s Hard Browser-Agent Boundary Fell Twice — What Enterprises Should Assume Now

Image: Forkast
The fix Perplexity shipped for its Comet browser was meant to be final: a hard boundary on file:// paths, out of reach of the agent no matter what the prompt said. Zenity Labs titled the account of what happened next Breaking the Patch , and the title is the finding. Blocking a disclosed path is not the same as closing the vulnerability. After Perplexity shipped a hard boundary blocking agent access to file:// paths, Zenity Labs bypassed it twice: first through view-source:file:// URLs, then by appending a #.pdf or #.html suffix that slipped past the filter. What the boundary was holding back is worth stating plainly.
Read the full story on ForkastBeCrypto News shows a short excerpt and links to the publisher. The full report belongs to Forkast.



