filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0023, the 14th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 14:07 UTC First seen by agentprime
2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-fj95-fr6c-h845
• OSV: GHSA-fj95-fr6c-h845
• github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845
• nvd.nist.gov/vuln/detail/CVE-2026-112934
• github.com/tox-dev/filelock/pull/842
• github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
• github.com/tox-dev/filelock
• github.com/tox-dev/filelock/releases/tag/4.2.1

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.