UBUNTU-CVE-2026-112913 (CVE-2026-112913)
Vulnerability from osv_ubuntu – Published: 2026-11-06 00:00 – Updated: 2026-11-06 00:00 – Source websitefilelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python-filelock",
"binary_version": "3.0.4-1ubuntu0.1~esm1"
},
{
"binary_name": "python3-filelock",
"binary_version": "3.0.4-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.0.4-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.0.11-1",
"2.0.12-1",
"2.0.13-1",
"3.0.0-2",
"3.0.3-1",
"3.0.4-1",
"3.0.4-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-filelock",
"binary_version": "3.0.12-2ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.0.12-2ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.12-1",
"3.0.12-2",
"3.0.12-2ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-filelock",
"binary_version": "3.6.0-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.6.0-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.12-2",
"3.3.2-1",
"3.4.0-1",
"3.4.2-1",
"3.4.2-2",
"3.6.0-1",
"3.6.0-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-filelock",
"binary_version": "3.13.1-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.13.1-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.12.2-1",
"3.12.4-1",
"3.13.1-1",
"3.13.1-1ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-filelock",
"binary_version": "3.32.2-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.32.2-1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.20.3-1",
"3.29.4-1",
"3.32.0-1",
"3.32.2-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-filelock",
"binary_version": "3.20.3-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "python-filelock",
"purl": "pkg:deb/ubuntu/python-filelock@3.20.3-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.18.0-1",
"3.20.0-1",
"3.20.2-1",
"3.20.3-1"
]
}
],
"aliases": [],
"details": "filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.",
"id": "UBUNTU-CVE-2026-112913",
"modified": "2026-11-06T00:00:00Z",
"published": "2026-11-06T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-112913"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112913"
},
{
"type": "REPORT",
"url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5"
},
{
"type": "REPORT",
"url": "https://github.com/tox-dev/filelock/pull/834"
},
{
"type": "REPORT",
"url": "https://github.com/tox-dev/filelock/pull/854"
},
{
"type": "REPORT",
"url": "https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b"
},
{
"type": "REPORT",
"url": "https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-112913"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.