Security Resilience

CVE-2026-112939

Tox-Dev Filelock 3.22.0 – 4.2.1

Public PoC
Published
20 October 2026
Modified
21 October 2026
Patch / advisory
CVSS Score v3.1 4.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0014 3th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-112939 is a medium-severity Insufficient Verification of Data Authenticity (CWE-345) vulnerability in Tox-Dev Filelock. Its CVSS base score is 4.7 (Medium).

Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can trust a forged process identifier in a marker that an attacker can modify but cannot remove, allowing an authorized contender such as another process of the…

more

holder's account or root to act as a confused deputy, remove the live marker, and admit another holder. This issue is fixed in version 4.2.1.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-112914Same product: Tox-Dev Filelock
CVE-2026-112937Same product: Tox-Dev Filelock
CVE-2026-112911Same product: Tox-Dev Filelock
CVE-2026-112935Same product: Tox-Dev Filelock
CVE-2026-112934Same product: Tox-Dev Filelock
CVE-2026-112909Same product: Tox-Dev Filelock
CVE-2026-112940Same product: Tox-Dev Filelock
CVE-2026-112915Same product: Tox-Dev Filelock
CVE-2025-68146Same product: Tox-Dev Filelock
CVE-2026-112912Same product: Tox-Dev Filelock

Affected Assets

tox-dev
filelock
3.22.0 — 4.2.1

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-345

Directly requires independent verification of matching output before adverse decisions, mitigating insufficient authenticity checks on data from external sources.

addresses: CWE-345

Use of approved PKI certificates provides verifiable data authenticity and origin for communications and artifacts.

addresses: CWE-345

Mandates provision of authenticity and integrity artifacts that enable verification of name/address resolution data.

addresses: CWE-345

Requires explicit verification of data authenticity from authoritative sources, preventing acceptance of unauthenticated resolution responses.

addresses: CWE-345

Control requires verification of data authenticity/integrity (e.g., checksums) after aggregation/packing, directly reducing exploitation of insufficient verification before transmission.

addresses: CWE-345

Time synchronization supports reliable freshness verification when checking data authenticity across systems or components.

addresses: CWE-345

Mandates verification of data authenticity for software, firmware, and information.

addresses: CWE-345

Provenance documentation and monitoring directly enables verification of authenticity for components and data throughout their history.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect missing or weak data authenticity verification.

prevents

Secure coding practices include implementing proper data authenticity checks.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References