{"items":[{"id":"NVI-00008847","kind":"vulnerability","title":"filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-69hj-f68j-2879","CVE-2026-112909"],"plain_summary":"GitHub lists this reviewed advisory for filelock. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2427426ba17bc95197e96ad0f1549ede"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-28T21:08:37.000Z","value":"6.1 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-01a5af11a841ce6468d0b1d9e1619325"},{"kind":"CVSS","as_of":"2026-10-27T21:04:56.090Z","value":"6.1 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-6958402df4b7bc0a42aaaadf60f4eee8"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.220%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.12625. Missing scores are unknown.","source_id":"sr-2427426ba17bc95197e96ad0f1549ede"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01a5af11a841ce6468d0b1d9e1619325","url":"https://github.com/advisories/GHSA-69hj-f68j-2879","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-69hj-f68j-2879","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-6958402df4b7bc0a42aaaadf60f4eee8","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112909","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-112909","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:44.915Z"},{"id":"sr-2427426ba17bc95197e96ad0f1549ede","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-112909","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.841Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01a5af11a841ce6468d0b1d9e1619325"],"technology":"filelock","known_exclusions":[],"conditions_summary":"`UnixFileLock`, the backend of `FileLock` and `AsyncFileLock` on Unix, empties whatever regular file it finds at the lock path once it holds the `flock` (a kernel lock on an open file). With an explicit `mode` it also chmods that file (sets its permission bits), whether or not this acquire created it. Another local user who can rename or hard-link one of the files of the user running the lock (below: the lock user) onto the lock path gets that file truncated by the lock user's next `acquire()`. A hard link is a second name for the same file. With a mode such as `0o666` the file, still owned by the lock user, also becomes readable and writable by that other user. The other user can then read and alter everything the lock user writes to it afterwards.\n\n`O_NOFOLLOW`, the defence added for the symlink variant (CVE-2025-68146), does not see a renamed file or a hard link. The rename route needs the file's directory to be writable without the sticky bit (a directory flag that lets only a file's owner remove or rename it). The hard-link route into a sticky directory such as `/tmp` needs `fs.protected_hardlinks=0`, a Linux kernel setting. Affected versions are every filelock release up to a","public_affected_ranges":["<= 4.2.0"]}],"null_published_at":"2026-11-07T14:01:58.745Z","source_updated_at":"2026-10-28T21:08:37.000Z","source_disclosed_at":"2026-10-28T21:08:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00008847","kind":"vulnerability","title":"filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-69hj-f68j-2879","CVE-2026-112909"],"plain_summary":"GitHub lists this reviewed advisory for filelock. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-6958402df4b7bc0a42aaaadf60f4eee8"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-28T21:08:37.000Z","value":"6.1 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-01a5af11a841ce6468d0b1d9e1619325"},{"kind":"CVSS","as_of":"2026-10-27T21:04:56.090Z","value":"6.1 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-6958402df4b7bc0a42aaaadf60f4eee8"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01a5af11a841ce6468d0b1d9e1619325","url":"https://github.com/advisories/GHSA-69hj-f68j-2879","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-69hj-f68j-2879","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-6958402df4b7bc0a42aaaadf60f4eee8","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112909","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-112909","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:44.915Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01a5af11a841ce6468d0b1d9e1619325"],"technology":"filelock","known_exclusions":[],"conditions_summary":"`UnixFileLock`, the backend of `FileLock` and `AsyncFileLock` on Unix, empties whatever regular file it finds at the lock path once it holds the `flock` (a kernel lock on an open file). With an explicit `mode` it also chmods that file (sets its permission bits), whether or not this acquire created it. Another local user who can rename or hard-link one of the files of the user running the lock (below: the lock user) onto the lock path gets that file truncated by the lock user's next `acquire()`. A hard link is a second name for the same file. With a mode such as `0o666` the file, still owned by the lock user, also becomes readable and writable by that other user. The other user can then read and alter everything the lock user writes to it afterwards.\n\n`O_NOFOLLOW`, the defence added for the symlink variant (CVE-2025-68146), does not see a renamed file or a hard link. The rename route needs the file's directory to be writable without the sticky bit (a directory flag that lets only a file's owner remove or rename it). The hard-link route into a sticky directory such as `/tmp` needs `fs.protected_hardlinks=0`, a Linux kernel setting. Affected versions are every filelock release up to a","public_affected_ranges":["<= 4.2.0"]}],"null_published_at":"2026-11-07T07:07:42.483Z","source_updated_at":"2026-10-28T21:08:37.000Z","source_disclosed_at":"2026-10-28T21:08:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:56:08.420Z"},{"id":"NVI-00008847","kind":"vulnerability","title":"filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-69hj-f68j-2879","CVE-2026-112909"],"plain_summary":"GitHub lists this reviewed advisory for filelock. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-01a5af11a841ce6468d0b1d9e1619325"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-28T21:08:37.000Z","value":"6.1 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-01a5af11a841ce6468d0b1d9e1619325"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01a5af11a841ce6468d0b1d9e1619325","url":"https://github.com/advisories/GHSA-69hj-f68j-2879","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-69hj-f68j-2879","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01a5af11a841ce6468d0b1d9e1619325"],"technology":"filelock","known_exclusions":[],"conditions_summary":"`UnixFileLock`, the backend of `FileLock` and `AsyncFileLock` on Unix, empties whatever regular file it finds at the lock path once it holds the `flock` (a kernel lock on an open file). With an explicit `mode` it also chmods that file (sets its permission bits), whether or not this acquire created it. Another local user who can rename or hard-link one of the files of the user running the lock (below: the lock user) onto the lock path gets that file truncated by the lock user's next `acquire()`. A hard link is a second name for the same file. With a mode such as `0o666` the file, still owned by the lock user, also becomes readable and writable by that other user. The other user can then read and alter everything the lock user writes to it afterwards.\n\n`O_NOFOLLOW`, the defence added for the symlink variant (CVE-2025-68146), does not see a renamed file or a hard link. The rename route needs the file's directory to be writable without the sticky bit (a directory flag that lets only a file's owner remove or rename it). The hard-link route into a sticky directory such as `/tmp` needs `fs.protected_hardlinks=0`, a Linux kernel setting. Affected versions are every filelock release up to a","public_affected_ranges":["<= 4.2.0"]}],"null_published_at":"2026-10-31T22:13:27.119Z","source_updated_at":"2026-10-28T21:08:37.000Z","source_disclosed_at":"2026-10-28T21:08:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:56:08.420Z"}],"next_cursor":null,"snapshot_revision":"42594"}