# WiX based installers are vulnerable to binary hijack when run as SYSTEM

Advisory record · `GHSA-rf39-3f98-xr7r`

- **Identifiers:** `GHSA-rf39-3f98-xr7r` · `CVE-2024-29187`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-732](https://cwe.mitre.org/data/definitions/732.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 25 Mar 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Mar 2024, 19:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wix` (NuGet): affected `<3.14.1 || >=4.0.0, <4.0.5`; fixed in `3.14.1`, `4.0.5`
- `WixToolset.Sdk` (NuGet): affected `<4.0.5`; fixed in `4.0.5`

## Machine-written summary

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

> The wix package (versions below 3.14.1, and 4.0.0 up to but not including 4.0.5) and WixToolset.Sdk (versions below 4.0.5) are affected. When a WiX-based bundle runs as SYSTEM, Burn copies binaries into C:\Windows\Temp, which standard users can write to, so a local low-privileged user can hijack those binaries and gain SYSTEM privileges. Upgrade wix to 3.14.1 or 4.0.5 and WixToolset.Sdk to 4.0.5.

Written 9 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.3 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 15:21 UTC: First seen by agentprime
- 31 Oct 2026, 15:21 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rf39-3f98-xr7r)

## Sources

- [GitHub Advisory Database: GHSA-rf39-3f98-xr7r](https://github.com/advisories/GHSA-rf39-3f98-xr7r)
- [OSV: GHSA-rf39-3f98-xr7r](https://osv.dev/vulnerability/GHSA-rf39-3f98-xr7r)
- <https://github.com/wixtoolset/issues/security/advisories/GHSA-rf39-3f98-xr7r>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-29187>
- <https://github.com/wixtoolset/wix/commit/75a8c75d4e02ea219008dc5af7d03869291d61f7>
- <https://github.com/wixtoolset/wix3/commit/6d372e5169f1a334a395cdf496443bc0732098e9>
- <https://github.com/wixtoolset/issues>

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-rf39-3f98-xr7r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rf39-3f98-xr7r/>. Everything for agents: <https://agentprime.io/llms.txt>.