Is CVE-2026-112939 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-112939 being exploited in the wild.

How severe is CVE-2026-112939?

Medium severity, with a CVSS score of 4.7, published 20 October 2026.

Which products and versions are affected?

filelock (PyPI) >= 3.22.0, <= 4.2.0, ECOSYSTEM:introduced=3.22.0,fixed=4.2.1; Tox-Dev Filelock 3.22.0 to 4.2.0.

How is CVE-2026-112939 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-112939?

Check whether you run filelock (PyPI) or Tox-Dev Filelock at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112939: filelock SoftFileLock PID spoofing privilege escalation

Q: Is there a fix for CVE-2026-112939?

Yes. filelock (PyPI): upgrade to 4.2.1 or later. Until then: Ensure the directory containing lock markers has the sticky bit set to prevent unauthorized file replacement by other users. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-112939 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-112939?

Check whether you run filelock (PyPI) or Tox-Dev Filelock at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-112939 · Severity: medium · CVSS 4.7 · Published 2026-10-20

filelock is a Python library providing cross-platform file locking for coordinating access to shared resources. A vulnerability in SoftFileLock allows an attacker with local access to forge process identifiers in lock markers, trick the library into believing a lock is free when it is not, and acquire locks held by other processes. This could lead to unauthorized access to resources, data corruption, or privilege escalation if combined with other vulnerabilities.

Technologies: filelock (PyPI), Tox-Dev Filelock. Vendors: PyPI, Tox-Dev.

Quick answers

Is CVE-2026-112939 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112939 being exploited in the wild.
How severe is CVE-2026-112939?: Medium severity, with a CVSS score of 4.7, published 20 October 2026.
Which products and versions are affected?: filelock (PyPI) >= 3.22.0, <= 4.2.0, ECOSYSTEM:introduced=3.22.0,fixed=4.2.1; Tox-Dev Filelock 3.22.0 to 4.2.0.
Is there a fix for CVE-2026-112939?: Yes. filelock (PyPI): upgrade to 4.2.1 or later. Until then: Ensure the directory containing lock markers has the sticky bit set to prevent unauthorized file replacement by other users. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112939 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-112939?: Check whether you run filelock (PyPI) or Tox-Dev Filelock at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

filelock (PyPI): upgrade to 4.2.1 or later
```
pip install "filelock>=4.2.1"
```

Ensure the directory containing lock markers has the sticky bit set to prevent unauthorized file replacement by other users.

Technical details

SoftFileLock determines lock availability by reading marker files and checking if the recorded process owner is alive. A flaw in marker validation allows an attacker to forge the NSpid line in /proc/<pid>/status by injecting a carriage return in the process name, causing the library to misread process identity and incorrectly consider a live lock holder as dead. Combined with the ability to modify marker content, an authorized local user can remove live markers and acquire locks they should not hold.

Affected products

tox-dev filelock 3.22.0 to 4.2.0

Identifiers

CVE-2026-112939
GHSA-rfpc-qcw5-3pc4

Timeline

2026-10-20: disclosed
2026-10-17: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.