filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. This issue is fixed in version 4.2.1.
CVE-2026-112907
LOWPre-NVD 2.52.5ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 2.5 from GitHub Security Advisory (severity: LOW) published 2026-10-23. A secondary CVSS source baseline 2.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-117813 (ENISA EUVD) · GHSA-567q-5qvw-pf92 (GitHub Security Advisories)Source: ENISA EUVD
2.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 2.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 2.5
- EG Score
- 2.5LOWhigh confidence
- EG Risk
- 27EG Risk 27/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity25% × 45%Impact severity (EG Severity): CVSS 2.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 1st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (2.5): severity, escalated by confirmed exploitation. This CVE's 2.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 2.5 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 23, 2026
Last Modified
November 10, 2026
References (5)
- security-advisories@githubhttps://github.com/tox-dev/filelock/commit/97d694a9a3ee1721d6c79a480174dfd9b060a080
- security-advisories@githubhttps://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
- security-advisories@githubhttps://github.com/tox-dev/filelock/pull/835
- security-advisories@githubhttps://github.com/tox-dev/filelock/releases/tag/4.2.1
- security-advisories@github · CISA-ADPhttps://github.com/tox-dev/filelock/security/advisories/GHSA-567q-5qvw-pf92Exploit
Vendor Advisories for CVE-2026-112907(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | filelock @ 4.2.1 (fixes >= 3.22.0, <= 4.2.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| filelock | 3.22.0 ... 4.2.0 (49 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 12× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-10 05:41 UTCEchelonGraph re-scored
- 2026-11-10 05:41 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-10 05:27 UTCEchelonGraph re-scored
- 2026-11-10 05:27 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-10 04:45 UTCEchelonGraph re-scored
- 2026-11-10 04:45 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-06 21:48 UTCEchelonGraph re-scored
- 2026-11-06 21:48 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-05 23:12 UTCENISA EUVD ID recordedEUVD-2026-117813 · Source: ENISA EUVD
- 2026-11-05 22:31 UTCEchelonGraph re-scored
- 2026-11-05 22:31 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-05 21:58 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-01 07:59 UTCGHSA enrichmentGHSA-567q-5qvw-pf92 · GitHub severity LOW · GitHub CVSS 2.5
- 2026-11-01 07:59 UTCEchelonGraph re-scored
- 2026-10-25 14:51 UTCEchelonGraph re-scored
- 2026-10-23 23:21 UTCEchelonGraph re-scoredFirst assessed: 2.5 LOW
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:filelock
Frequently asked(5)
What is CVE-2026-112907?
CVE-2026-112907 is a low-severity vulnerability; its CVE record was published on October 23, 2026. filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read…
When was the CVE record for CVE-2026-112907 published?
The CVE record for CVE-2026-112907 was published on October 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-112907 actively exploited?
CVE-2026-112907 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112907?
CVE-2026-112907 has a CVSS base score of 2.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112907?
A fix for CVE-2026-112907 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112907 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-112907
Is Your Infrastructure Affected by CVE-2026-112907?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.