Approved changes feed: RSS · Atom
cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tox Dev (6e485f1a-f301-5f7c-8685-bf5a9b836878) |
|---|---|
| Product | Filelock (6b085a26-1444-5bb0-9140-396b3a165dd0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/tox-dev/filelock |
purl2cpe | 2026-06-01 10:16:59.231683 |
pkg:pypi/filelock |
purl2cpe | 2026-06-01 10:16:59.231686 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-112935 |
vulnerable | 2026-11-03 10:16:28.887834 |
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
MEDIUM (4.7)
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.
Published: 2026-10-20T14:32:25.740Z
Updated: 2026-10-28T14:17:06.745Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112939 |
vulnerable | 2026-11-03 10:16:28.875047 |
filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker
MEDIUM (4.7)
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 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.
Published: 2026-10-20T14:38:52.373Z
Updated: 2026-10-20T15:14:56.836Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112914 |
vulnerable | 2026-11-03 10:16:28.814982 |
filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory
MEDIUM (5.3)
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. This issue is fixed in version 4.2.1.
Published: 2026-10-20T14:26:18.813Z
Updated: 2026-10-21T15:55:21.992Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112909 |
vulnerable | 2026-11-03 10:16:28.789970 |
filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path
MEDIUM (6.1)
filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. This issue is fixed in version 4.2.1.
Published: 2026-10-20T14:16:02.317Z
Updated: 2026-10-22T21:25:25.906Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112911 |
vulnerable | 2026-11-03 10:16:28.620199 |
filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion
MEDIUM (6.3)
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. This issue is fixed in version 4.2.1.
Published: 2026-10-20T14:21:24.480Z
Updated: 2026-10-28T15:09:43.507Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112915 |
vulnerable | 2026-11-03 10:16:28.578271 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112934 |
vulnerable | 2026-11-03 10:16:28.479572 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112940 |
vulnerable | 2026-11-03 10:16:28.461534 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112936 |
vulnerable | 2026-11-03 10:16:28.261485 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112906 |
vulnerable | 2026-11-03 10:16:28.130943 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112937 |
vulnerable | 2026-11-03 10:16:28.120434 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112941 |
vulnerable | 2026-11-03 10:16:28.096335 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112912 |
vulnerable | 2026-11-03 10:16:28.062528 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22701 |
vulnerable | 2026-06-08 07:51:13.634909 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-68146 |
vulnerable | 2026-06-08 07:41:20.875813 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.