{"items":[{"id":"NVI-00008913","kind":"vulnerability","title":"filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders","revision":4,"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-fq56-3cx3-fjxp","CVE-2026-112935"],"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-05f596d0842fe0790217240b7c2cb34e"],"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:09.000Z","value":"4.7 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2b51184ad3404e8bdeb18c7ff08fa886"},{"kind":"CVSS","as_of":"2026-10-28T15:17:02.940Z","value":"4.7 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3df6e533339c6c23a1ce9945c39d253c"},{"kind":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.132%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.02795. Missing scores are unknown.","source_id":"sr-05f596d0842fe0790217240b7c2cb34e"}],"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-2b51184ad3404e8bdeb18c7ff08fa886","url":"https://github.com/advisories/GHSA-fq56-3cx3-fjxp","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fq56-3cx3-fjxp","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-3df6e533339c6c23a1ce9945c39d253c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112935","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-112935","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:44.915Z"},{"id":"sr-05f596d0842fe0790217240b7c2cb34e","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-112935","publisher":"FIRST EPSS","observed_at":"2026-11-06T00:24:57.630Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b51184ad3404e8bdeb18c7ff08fa886"],"technology":"filelock","known_exclusions":[],"conditions_summary":"The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the \"not implemented\" error) recognises the marker it judged stale by two values. The marker is the lock file at ``, whose presence says a process holds the lock. The values are its inode number (the kernel's identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.\n\nOn a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder's marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock's directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file's owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processe","public_affected_ranges":[">= 3.22.0, <= 4.2.0"]}],"null_published_at":"2026-11-07T07:07:46.833Z","source_updated_at":"2026-10-28T21:08:09.000Z","source_disclosed_at":"2026-10-28T21:08:08.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-00008913","kind":"vulnerability","title":"filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders","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-fq56-3cx3-fjxp","CVE-2026-112935"],"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-3b2317440503302392eecf06761b117e"],"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:09.000Z","value":"4.7 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2b51184ad3404e8bdeb18c7ff08fa886"},{"kind":"CVSS","as_of":"2026-10-28T15:17:02.940Z","value":"4.7 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3df6e533339c6c23a1ce9945c39d253c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.132%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.02756. Missing scores are unknown.","source_id":"sr-3b2317440503302392eecf06761b117e"}],"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-2b51184ad3404e8bdeb18c7ff08fa886","url":"https://github.com/advisories/GHSA-fq56-3cx3-fjxp","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fq56-3cx3-fjxp","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-3df6e533339c6c23a1ce9945c39d253c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112935","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-112935","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:44.915Z"},{"id":"sr-3b2317440503302392eecf06761b117e","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-112935","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.374Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b51184ad3404e8bdeb18c7ff08fa886"],"technology":"filelock","known_exclusions":[],"conditions_summary":"The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the \"not implemented\" error) recognises the marker it judged stale by two values. The marker is the lock file at ``, whose presence says a process holds the lock. The values are its inode number (the kernel's identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.\n\nOn a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder's marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock's directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file's owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processe","public_affected_ranges":[">= 3.22.0, <= 4.2.0"]}],"null_published_at":"2026-11-04T10:04:35.937Z","source_updated_at":"2026-10-28T21:08:09.000Z","source_disclosed_at":"2026-10-28T21:08:08.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-00008913","kind":"vulnerability","title":"filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fq56-3cx3-fjxp","CVE-2026-112935"],"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-3b2317440503302392eecf06761b117e"],"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:09.000Z","value":"4.7 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2b51184ad3404e8bdeb18c7ff08fa886"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.132%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.02756. Missing scores are unknown.","source_id":"sr-3b2317440503302392eecf06761b117e"}],"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-2b51184ad3404e8bdeb18c7ff08fa886","url":"https://github.com/advisories/GHSA-fq56-3cx3-fjxp","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fq56-3cx3-fjxp","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"},{"id":"sr-3b2317440503302392eecf06761b117e","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-112935","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.374Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b51184ad3404e8bdeb18c7ff08fa886"],"technology":"filelock","known_exclusions":[],"conditions_summary":"The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the \"not implemented\" error) recognises the marker it judged stale by two values. The marker is the lock file at ``, whose presence says a process holds the lock. The values are its inode number (the kernel's identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.\n\nOn a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder's marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock's directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file's owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processe","public_affected_ranges":[">= 3.22.0, <= 4.2.0"]}],"null_published_at":"2026-10-31T22:27:15.296Z","source_updated_at":"2026-10-28T21:08:09.000Z","source_disclosed_at":"2026-10-28T21:08:08.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-00008913","kind":"vulnerability","title":"filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fq56-3cx3-fjxp","CVE-2026-112935"],"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-2b51184ad3404e8bdeb18c7ff08fa886"],"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:09.000Z","value":"4.7 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-2b51184ad3404e8bdeb18c7ff08fa886"}],"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-2b51184ad3404e8bdeb18c7ff08fa886","url":"https://github.com/advisories/GHSA-fq56-3cx3-fjxp","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fq56-3cx3-fjxp","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:08.420Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b51184ad3404e8bdeb18c7ff08fa886"],"technology":"filelock","known_exclusions":[],"conditions_summary":"The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the \"not implemented\" error) recognises the marker it judged stale by two values. The marker is the lock file at ``, whose presence says a process holds the lock. The values are its inode number (the kernel's identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.\n\nOn a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder's marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock's directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file's owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processe","public_affected_ranges":[">= 3.22.0, <= 4.2.0"]}],"null_published_at":"2026-10-31T22:13:27.122Z","source_updated_at":"2026-10-28T21:08:09.000Z","source_disclosed_at":"2026-10-28T21:08:08.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"}