CVE-2026-112910 json
filelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACL
published 2026-10-28 11 d ago modified 2026-11-06 2 d ago also GHSA-8mx5-7m5m-r77g , EUVD-2026-117809
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
filelock is a platform-independent file lock for Python. From 3.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory's inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. This issue is fixed in version 4.2.1.
Patch / fix
- pypi filelock 4.2.1
- github.com/tox-dev/filelock@72786d4 commit
- github.com/tox-dev/filelock@e1e825b commit
- github.com/tox-dev/filelock#835 pull request
- github.com/tox-dev/filelock/releases/tag/4.2.1 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-112910 updated cvss 5.3
filelock: filelock: Denial of Service via improper lock file permissions on Windows
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | filelock | >=3.10.0, <4.2.1 |
4.2.1 |
Affected products
- tox-dev filelock
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/tox-dev/filelock/pull/835
web
- github.com /tox-dev/filelock/commit/72786d41aa25159ad28c1bcf4291738b135b2c6c
-
github.com
/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
web
-
github.com
/tox-dev/filelock/security/advisories/GHSA-8mx5-7m5m-r77g
web
-
github.com
/tox-dev/filelock/releases/tag/4.2.1
web
-
github.com
/tox-dev/filelock
package
Sources
- CVE List CVE-2026-112910
- GitHub Advisory GHSA-8mx5-7m5m-r77g
- NVD CVE-2026-112910
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.