Skip to content
Heist/ feed
Medium

filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

Type: advisorySource: Official CVE List1 source record

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.

Announced Source revision 1
Original source ↗

CVE-2026-112937

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: cve:CVE-2026-112937

filelock

Source reference: /containers/cna/affected/0/product

Affected versions
Not stated in this record
Fixed versions
Not stated in this record
Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "vendor": "tox-dev",
    "product": "filelock",
    "versions": [
      {
        "status": "affected",
        "version": ">= 4.1.0, < 4.2.1"
      }
    ]
  }
]
Related CVEs
CVE-2026-112937

Source reference: /cveMetadata/cveId

Publisher severity

medium

Source reference: /containers/cna/metrics

Event
#49199 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement