BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-71176High confidence

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

pytest · pytest

6.8MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs pytest pytest and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepytestAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepytestAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepytestAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepytestAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepytestUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIpytestECOSYSTEM: introduced 0; fixed 9.0.39.0.3OSV record ↗aggregator derived · 10 Sep 2026
pippytest< 9.0.39.0.3GitHub advisory ↗github reviewed aggregator · 13 Apr 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-4171

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

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.

What

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.

Why

The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Creation of Temporary File in Directory with Insecure Permissions → disrupt the affected service
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-379 ↗

CWE-379: Creation of Temporary File in Directory with Insecure Permissions. The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedDenial of serviceCWE-379
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260128Security Bulletin 28 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Jan 2026, published on 28 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-59471 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71176 https://www.cve.org/CVERecord?id=CVE-2025-71176 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-0636 https://www.cve.org/CVERecord?id=CVE-2026-0636 Référence CVE CVE-2026-10723 https://www.cve.org/CVERecord?id=CVE-2026-10723 Référence CVE CVE-2026-10805 https://www.cve.org/CVERecord?id=CVE-2026-10805 Référence CVE CVE-2026-11622 https://www.cve.org/CVERecord?id=CVE-2026-11622 Référence CVE CVE-2026-11721 https://www.cve.org/CVERecord?id=CVE-2026-11721 Référence CVE CVE-2026-11822 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-66418 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-67724 https://www.cve.org/CVERecord?id=CVE-2025-67724 Référence CVE CVE-2025-67725 https://www.cve.org/CVERecord?id=CVE-2025-67725 Référence CVE CVE-2025-67726 https://www.cve.org/CVERecord?id=CVE-2025-67726 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-68470 https://www.cve.org/CVERecord?id=CVE-2025-68470 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71176 https://www.cve.org/CVERecord?id=CVE-2025-71176 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-10535 https://www.cve.org/CVERecord?id=CVE-2026-10535 Référence CVE CVE-2026-10842 https://www.cve.org/CVERecord?id=CVE-2026-10842 Référence CVE CVE-2026-11595 https://www.cve.org/CVERecord?id=CVE-2026-11595 Référence CVE CVE-2026-11708 https://www.cve.org/CVERecord?id=CVE-2026-11708 Référence CVE CVE-2026-11712 https://www.cve.org/CVERecord?id=CVE-2026-11712 Référence CVE CVE-2026-12143 https://www.cve.org/CVERecord?id=CVE-2026-12143 Référence CVE CVE-2026-14501 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
pytest: ≤ 9.0.2
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 Jan 2026 · Last source change 22 Jan 2026, 12:26 UTC · CWE-379 · Creation of Temporary File in Directory with Insecure Permissions

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-4171
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-71176 · cve.blacktree.nl