# microsandbox: Secret values exposed in world-readable process arguments

Advisory record · `GHSA-m8f5-rh7h-vgg3`

- **Identifiers:** `GHSA-m8f5-rh7h-vgg3` · `CVE-2026-61670`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-214](https://cwe.mitre.org/data/definitions/214.html)
- **Tags:** [CWE-214](https://agentprime.io/advisories/tag/cwe-214.md)
- **Published:** 22 Sept 2026
- **Updated:** 22 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Sept 2026, 19:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `microsandbox` (crates.io): affected `<0.5.10`; fixed in `0.5.10`

## Machine-written summary

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

> Microsandbox versions before 0.5.10 pass the full network configuration, including real secret values, and any per-sandbox environment values as command-line arguments to the sandbox child process. Any local user or co-resident process on the same host can read these secrets from the process listing (for example via /proc or ps) for as long as the sandbox runs. Upgrade to microsandbox 0.5.10, which fixes the issue.

Written 3 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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m8f5-rh7h-vgg3)

## Sources

- [GitHub Advisory Database: GHSA-m8f5-rh7h-vgg3](https://github.com/advisories/GHSA-m8f5-rh7h-vgg3)
- [OSV: GHSA-m8f5-rh7h-vgg3](https://osv.dev/vulnerability/GHSA-m8f5-rh7h-vgg3)
- <https://github.com/superradcompany/microsandbox/security/advisories/GHSA-m8f5-rh7h-vgg3>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-61670>
- <https://github.com/superradcompany/microsandbox/issues/997>
- <https://github.com/superradcompany/microsandbox/pull/1006>
- <https://github.com/superradcompany/microsandbox/commit/2ac6a177b11212d392bf1e7dc77aaf14e4768aa8>
- <https://github.com/superradcompany/microsandbox/commit/fbfb2366bfafad5e6df8778183f95fd8ca3c00a4>
- <https://github.com/superradcompany/microsandbox>
- <https://github.com/superradcompany/microsandbox/releases/tag/v0.5.10>

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-m8f5-rh7h-vgg3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m8f5-rh7h-vgg3/>. Everything for agents: <https://agentprime.io/llms.txt>.