CVE-2025-71176: pytest has vulnerable tmpdir handling
Affects pytestSource GCVE Database
Not known to be exploited · CVSS 6.8 Medium : upgrade to 9.0.3 when convenient.
Data as of 30 Oct 2026, 05:15 UTC
- Patch
- Available – fixed in 9.0.3
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade pytest to 9.0.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewpytestpkg:brew/pytestOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
pytest through 9.0.2 on UNIX relies on directories with the `/tmp/pytest-of-{user}` name pattern, which allows local users to cause a denial of service or possibly gain privileges.
References
- nvd.nist.gov/vuln/detail/CVE-2025-71176 (opens in a new tab)
- github.com/pytest-dev/pytest/issues/13669 (opens in a new tab)
- github.com/pytest-dev/pytest/pull/14343 (opens in a new tab)
- github.com/pytest-dev/pytest/commit/95d8423bd24992deea5b9df32555fa1741679e2c (opens in a new tab)
- github.com/pytest-dev/pytes (opens in a new tab)
- github.com/pytest-dev/pytest/releases/tag/9.0.3 (opens in a new tab)
- openwall.com/lists/oss-security/2026/01/21/5 (opens in a new tab)