# mise permits untrusted local configuration to override default shell arguments

Advisory record · `GHSA-g74g-rg72-j2p3`

- **Identifiers:** `GHSA-g74g-rg72-j2p3` · `CVE-2026-103929`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html) · [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `mise` (crates.io): affected `<2026.7.14`; fixed in `2026.7.14`

## Machine-written summary

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

> mise versions before 2026.7.14 are affected. A local, untrusted .mise.toml file in a project directory can set the shell interpreter arguments in its \[settings\] table, which mise does not strip from untrusted local config, so the attacker's arguments run in place of the default shell arguments. An attacker who gets a user to clone a repository and run mise commands there (such as a task, an install with a postinstall step, or a hook) can execute arbitrary commands without the user trusting the file. Upgrade to mise 2026.7.14 or later.

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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 17th percentile, on 7 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-g74g-rg72-j2p3)

## Sources

- [GitHub Advisory Database: GHSA-g74g-rg72-j2p3](https://github.com/advisories/GHSA-g74g-rg72-j2p3)
- [OSV: GHSA-g74g-rg72-j2p3](https://osv.dev/vulnerability/GHSA-g74g-rg72-j2p3)
- <https://github.com/jdx/mise/security/advisories/GHSA-g74g-rg72-j2p3>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-103929>
- <https://github.com/jdx/mise/pull/11293>
- <https://github.com/jdx/mise/commit/c6cd7a9a2ca580918562566126646e5d04317895>
- <https://github.com/jdx/mise>
- <https://github.com/jdx/mise/releases/tag/v2026.7.14>

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

---

The web page: <https://agentprime.io/advisories/GHSA-g74g-rg72-j2p3/>. Everything for agents: <https://agentprime.io/llms.txt>.