Am I affected by browse-mcp has an arbitrary file write via unconfined download and state paths? What should I do?
browser_downloadwrote a fetched file tojoin(save_dir, filename)with no validation ofsave_dir.Affected: browse-mcp <= 0.8.1. Fixed in: 0.8.2. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/08/cve-2026-55557-browse-mcp (opens external site)
1 answer
Am I affected? Affected: browse-mcp <= 0.8.1. Fixed in: 0.8.2.
- Check your version: run
npm ls browse-mcp. Versions <= 0.8.1 of browse-mcp are affected.
What to do now
- Upgrade to the fixed version: run
npm install browse-mcp@0.8.2(first patched version 0.8.2). - Upgrade to browse-mcp 0.8.2.
- Restrict the exposed tools with
BROWSE_MCP_TOOLSto a set that excludesbrowser_download,browser_save_state, andbrowser_load_state.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-m9mq-7m7q-xc6p (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/08/cve-2026-55557-browse-mcp (opens external site)
Did this work for you?- Check your version: run