# Magic Wormhole: "wormhole receive" allows arbitrary local file overwrite

Advisory record · `GHSA-4g4c-mfqg-pj8r`

- **Identifiers:** `GHSA-4g4c-mfqg-pj8r` · `CVE-2026-32116` · `PYSEC-2026-2615`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 13 Mar 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Mar 2026, 15:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `magic-wormhole` (PyPI): affected `>=0.21.0, <0.23.0`; fixed in `0.23.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Magic Wormhole versions 0.21.0 up to but not including 0.23.0 (PyPI magic-wormhole) let a sender overwrite arbitrary local files when the receiver runs "wormhole receive", including files such as \~/.ssh/authorized_keys and .bashrc. Only the party sending the file can carry out this attack, which could lead to compromise of the receiver's computer. Upgrade to magic-wormhole 0.23.0, which fixes the issue; until then, receivers can use the --output or -o option on every "wormhole receive" or "wormhole rx" command to set the destination filename themselves.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.2 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0040, the 34th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4g4c-mfqg-pj8r)

## Sources

- [GitHub Advisory Database: GHSA-4g4c-mfqg-pj8r](https://github.com/advisories/GHSA-4g4c-mfqg-pj8r)
- [OSV: GHSA-4g4c-mfqg-pj8r](https://osv.dev/vulnerability/GHSA-4g4c-mfqg-pj8r)
- <https://github.com/magic-wormhole/magic-wormhole/security/advisories/GHSA-4g4c-mfqg-pj8r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32116>
- <https://github.com/magic-wormhole/magic-wormhole>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4g4c-mfqg-pj8r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4g4c-mfqg-pj8r/>. Everything for agents: <https://agentprime.io/llms.txt>.
