{"api_version":"1","generated_at":"2026-10-22T17:54:37+00:00","cve":"CVE-2026-112909","urls":{"html":"https://cve.report/CVE-2026-112909","api":"https://cve.report/api/cve/CVE-2026-112909.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-112909","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-112909"},"summary":{"title":"filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path","description":"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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-10-20 15:17:15","updated_at":"2026-10-20 19:50:26"},"problem_types":["CWE-706","CWE-706 CWE-706: Use of Incorrectly-Resolved Name or Reference"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"6.1","severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","baseScore":6.1,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"6.1","severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","data":{"attackComplexity":"LOW","attackVector":"LOCAL","availabilityImpact":"NONE","baseScore":6.1,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879","name":"https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/tox-dev/filelock/releases/tag/4.2.1","name":"https://github.com/tox-dev/filelock/releases/tag/4.2.1","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a","name":"https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/tox-dev/filelock/pull/835","name":"https://github.com/tox-dev/filelock/pull/835","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-112909","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112909","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"tox-dev","product":"filelock","version":"affected < 4.2.1","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"filelock","vendor":"tox-dev","versions":[{"status":"affected","version":"< 4.2.1"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"LOCAL","availabilityImpact":"NONE","baseScore":6.1,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-706","description":"CWE-706: Use of Incorrectly-Resolved Name or Reference","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-20T14:16:02.317Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879","tags":["x_refsource_CONFIRM"],"url":"https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879"},{"name":"https://github.com/tox-dev/filelock/pull/835","tags":["x_refsource_MISC"],"url":"https://github.com/tox-dev/filelock/pull/835"},{"name":"https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a","tags":["x_refsource_MISC"],"url":"https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a"},{"name":"https://github.com/tox-dev/filelock/releases/tag/4.2.1","tags":["x_refsource_MISC"],"url":"https://github.com/tox-dev/filelock/releases/tag/4.2.1"}],"source":{"advisory":"GHSA-69hj-f68j-2879","discovery":"UNKNOWN"},"title":"filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-112909","datePublished":"2026-10-20T14:16:02.317Z","dateReserved":"2026-10-19T20:16:09.857Z","dateUpdated":"2026-10-20T14:16:02.317Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-20 15:17:15","lastModifiedDate":"2026-10-20 19:50:26","problem_types":["CWE-706","CWE-706 CWE-706: Use of Incorrectly-Resolved Name or Reference"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","baseScore":6.1,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":1.8,"impactScore":4.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"112909","Ordinal":"1","Title":"filelock: UnixFileLock truncates and chmods any regular file ano","CVE":"CVE-2026-112909","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"112909","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"filelock: UnixFileLock truncates and chmods any regular file ano"}]}}}