CVE-2026-112936

Published: Ott 20, 2026 Last Modified: Ott 20, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,1
Attack Vector: local
Attack Complexity: low
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: none
Integrity: high
Availability: low

Description

AI Translation Available

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory to redirect database creation and locking or split mutual exclusion between targets. This issue is fixed in version 4.0.9.

59

Improper Link Resolution Before File Access ('Link Following')

Draft
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control Other
Potential Impacts:
Read Files Or Directories Modify Files Or Directories Bypass Protection Mechanism Execute Unauthorized Code Or Commands
Applicable Platforms
Operating Systems: Windows, Unix
View CWE Details
668

Exposure of Resource to Wrong Sphere

Draft
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Other
Potential Impacts:
Read Application Data Modify Application Data Varies By Context
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56
https://github.com/tox-dev/filelock/commit/4d45e83caf7e31f9a12fb44526bdc07f7011…
https://github.com/tox-dev/filelock/releases/tag/4.0.9
https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56