{"items":[{"id":"NVI-00010572","kind":"vulnerability","title":"filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database","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-9vhv-jxww-xfm5","CVE-2026-112913"],"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-0b8b00d6326dbae3be1fd2a809172ebb"],"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-23T22:28:20.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4c3db70939ff9a89c4e38de95e9ee109"},{"kind":"CVSS","as_of":"2026-11-06T21:40:43.450Z","value":"3.3 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-0b8b00d6326dbae3be1fd2a809172ebb"}],"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-4c3db70939ff9a89c4e38de95e9ee109","url":"https://github.com/advisories/GHSA-9vhv-jxww-xfm5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-9vhv-jxww-xfm5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-0b8b00d6326dbae3be1fd2a809172ebb","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112913","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-112913","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-07T00:52:39.494Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4c3db70939ff9a89c4e38de95e9ee109"],"technology":"filelock","known_exclusions":[],"conditions_summary":"On Windows, `ReadWriteLock` and `AsyncReadWriteLock` (the SQLite-backed reader/writer lock) connect SQLite to the lock database by its path, in every directory. SQLite derives three side files from that path: `-journal`, the rollback journal (pages saved to undo an interrupted write); `-wal`, the write-ahead log (changes kept outside the main file); and `-shm`, the shared-memory index of the WAL. SQLite acts on whichever of these it finds beside the database before the lock runs any statement. Another local account that can create files in the database's directory, but not delete files of other accounts there, places such a side file beside the database and denies everyone `DELETE` on it, which a file's creator may do. `C:\\Windows\\Temp` (the temporary directory of services, granting `BUILTIN\\Users` create but not delete) and `C:\\Users\\Public` are such directories.\n\nWith a `-wal` in place, every `read_lock()` and `write_lock()` of the user running the lock (below: the lock user) raises `sqlite3.OperationalError: disk I/O error` at once, whatever `timeout` says, until that account removes its file; the lock user cannot. With a `-journal` beside a lock da","public_affected_ranges":[">= 3.20.4, <= 4.2.0"]}],"null_published_at":"2026-11-07T18:43:12.062Z","source_updated_at":"2026-10-23T22:28:20.000Z","source_disclosed_at":"2026-10-23T22:28:19.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-31T22:07:08.657Z"},{"id":"NVI-00010572","kind":"vulnerability","title":"filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9vhv-jxww-xfm5","CVE-2026-112913"],"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-4c3db70939ff9a89c4e38de95e9ee109"],"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-23T22:28:20.000Z","value":"3.3 low","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4c3db70939ff9a89c4e38de95e9ee109"}],"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-4c3db70939ff9a89c4e38de95e9ee109","url":"https://github.com/advisories/GHSA-9vhv-jxww-xfm5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-9vhv-jxww-xfm5","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4c3db70939ff9a89c4e38de95e9ee109"],"technology":"filelock","known_exclusions":[],"conditions_summary":"On Windows, `ReadWriteLock` and `AsyncReadWriteLock` (the SQLite-backed reader/writer lock) connect SQLite to the lock database by its path, in every directory. SQLite derives three side files from that path: `-journal`, the rollback journal (pages saved to undo an interrupted write); `-wal`, the write-ahead log (changes kept outside the main file); and `-shm`, the shared-memory index of the WAL. SQLite acts on whichever of these it finds beside the database before the lock runs any statement. Another local account that can create files in the database's directory, but not delete files of other accounts there, places such a side file beside the database and denies everyone `DELETE` on it, which a file's creator may do. `C:\\Windows\\Temp` (the temporary directory of services, granting `BUILTIN\\Users` create but not delete) and `C:\\Users\\Public` are such directories.\n\nWith a `-wal` in place, every `read_lock()` and `write_lock()` of the user running the lock (below: the lock user) raises `sqlite3.OperationalError: disk I/O error` at once, whatever `timeout` says, until that account removes its file; the lock user cannot. With a `-journal` beside a lock da","public_affected_ranges":[">= 3.20.4, <= 4.2.0"]}],"null_published_at":"2026-10-31T22:27:09.623Z","source_updated_at":"2026-10-23T22:28:20.000Z","source_disclosed_at":"2026-10-23T22:28:19.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-31T22:07:08.657Z"}],"next_cursor":null,"snapshot_revision":"42594"}