# PHPUnit vulnerable to code execution by other local users via shared temporary directory in PHPT code coverage handling

Advisory record · `GHSA-9vw2-f4vp-x7gf`

- **Identifiers:** `GHSA-9vw2-f4vp-x7gf` · `CVE-2026-119193` · `PKSA-qhjm-rpqc-qkn6`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-379](https://cwe.mitre.org/data/definitions/379.html)
- **Tags:** [CWE-379](https://agentprime.io/advisories/tag/cwe-379.md)
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `phpunit/phpunit` (Packagist): affected `>=13.4.0, <13.4.4`; fixed in `13.4.4`

## Machine-written summary

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

> PHPUnit versions 13.4.0 through 13.4.3 (fixed in 13.4.4) are vulnerable when PHPT tests run with code coverage on a system where the temporary files directory is shared between users, such as Linux with a shared /tmp. A local user with an account on the same system can create the fixed-name directory before the developer runs the tests, then replace the PHPT test code so it executes with the developer's privileges, without the test result or coverage report showing a change. Upgrade to PHPUnit 13.4.4, which uses an unpredictable directory name accessible only to the current user.

Written 31 Oct 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:53 UTC: First seen by agentprime
- 31 Oct 2026, 13:53 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9vw2-f4vp-x7gf)

## Sources

- [GitHub Advisory Database: GHSA-9vw2-f4vp-x7gf](https://github.com/advisories/GHSA-9vw2-f4vp-x7gf)
- [OSV: GHSA-9vw2-f4vp-x7gf](https://osv.dev/vulnerability/GHSA-9vw2-f4vp-x7gf)
- <https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-9vw2-f4vp-x7gf>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-119193>
- <https://github.com/sebastianbergmann/phpunit/commit/ae31c78a86e9d6c641497bacf47462d7bb7d7f34>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/phpunit/phpunit/CVE-2026-119193.yaml>
- <https://github.com/sebastianbergmann/phpunit>
- <https://github.com/sebastianbergmann/phpunit/releases/tag/13.4.4>

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-9vw2-f4vp-x7gf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9vw2-f4vp-x7gf/>. Everything for agents: <https://agentprime.io/llms.txt>.