Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

browse-mcp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6npmPublished

    browse-mcp has an arbitrary file write via unconfined download and state paths

    CVE-2026-55557 · GHSA-m9mq-7m7q-xc6p

    Affected
    • npm browse-mcp <= 0.8.1
    Fixed in
    0.8.2· Vendor fix available
    Issue
    Impact browserdownload wrote a fetched file to join(savedir, filename) with no validation of savedir, and browsersavestate / browserloadstate honored an explicit path unchanged. The MCP caller controls these arguments (a malicious MCP client, or an autonomous agent steered by indirect prompt injection on a visited page), so an attacker could supply an arbitrary savedir (or state path) together with a URL whose response body became the file contents, writing attacker-controlled bytes to any path the process can reach (for example ~/.bashrc, an autostart entry, or a cron file). That is an arbitrary file write that can lead to host code execution. The forcefetch fallback additionally used a raw fetch() that bypassed the BROWSEMCPALLOWEDORIGINS origin fence. Estimated severity: CVSS 3.1 around 7.8 (High) for the local / agent-mediated case. Patches Fixed in 0.8.2. savedir is confined under the download root (~/.browse-mcp/downloads) and the explicit state path under ~/.browse-mcp/state;…

    Recommended action: Upgrade to 0.8.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →