CVE-2026-112934
filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record
Auswirkung
filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1.
Ein Angreifer kann die Lücke mit lokalem Zugriff auf das System ausnutzen, mit einem normalen Benutzerkonto, ohne Zutun eines Nutzers. Bei Erfolg: geringes Risiko, dass Daten oder Systeme verändert werden, hohes Risiko für Ausfälle.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| pip | filelock | >= 4.0.0, <= 4.2.0 | 4.2.1 |
Betroffene Produkte · Tox-dev
| Produkt | Betroffene Versionen |
|---|---|
| Filelock | ab 4.0.0 vor 4.2.1 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://github.com/advisories/GHSA-fj95-fr6c-h845
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845
- https://nvd.nist.gov/vuln/detail/CVE-2026-112934
- https://github.com/tox-dev/filelock/pull/842
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- https://github.com/tox-dev/filelock/releases/tag/4.2.1