CVE-2026-1129116.3MediumCWE-283

CVE-2026-112911: filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

tox-dev · filelock

Affected: tox-dev filelock · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.1%probability of exploitation in the next 30 days

4th percentile

050100

Higher than 4% of scored CVEs

6.3MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. This issue is fixed in version 4.2.1.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

tox-dev · filelock>= 3.30.0, < 4.2.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Unverified Ownership · Access Control
Vendor: tox-dev
Published: October 2026
Band: Unlikely (under 1%), October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-112911 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.