CVE-2026-112935
Received Received - Intake

Race Condition in filelock Leads to File Lock Bypass

Vulnerability report for CVE-2026-112935, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: GitHub, Inc.

Description

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-10-20
AI Q&A
2026-10-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tox-dev filelock >= 3.22.0, < 4.2.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-112935 is a race condition vulnerability in the filelock library versions 3.22.0 to 4.2.0. It allows two processes to hold the same lock simultaneously under specific conditions. An attacker with local access can exploit this by creating a stale lock file with a future modification time, forcing the lock to be released prematurely. When the inode number is reused by the filesystem, another process can acquire the lock without detection.

Detection Guidance

Check if your system uses filelock library versions 3.22.0 to 4.2.0. Run: pip show filelock or pip list | grep filelock to verify the installed version. Inspect lock files in sticky directories like /tmp for unexpected lock file behavior or premature lock releases.

Impact Analysis

This vulnerability can lead to high integrity loss. Two processes may write to protected data simultaneously without awareness of each other, causing data corruption or inconsistencies. This requires a sticky shared directory, filesystem support for inode reuse, and at least two contending processes.

Mitigation Strategies

Upgrade the filelock library to version 4.2.1 or later. Use pip install --upgrade filelock. Ensure no processes rely on the vulnerable versions. Review lock file handling in applications using filelock, especially in shared directories with sticky bits.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-112935. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart