filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. This issue is fixed in version 4.2.1.
CVE-2026-112940
HIGHPre-NVD 7.17.1ElevatedEG-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 scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-105031 (ENISA EUVD) · GHSA-v4x8-3wr5-3wq8 (GitHub Security Advisories)Source: ENISA EUVD
7.1EG
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.2%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 48EG Risk 48/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)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 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.2%
- EPSS %ILE
- 8th
- 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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS. 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: 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.
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 20, 2026
Last Modified
October 22, 2026
Advisory Details (4)
Auto-updated Oct 20, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available
4.2.1
Patch available: tox-dev/filelock 4.2.1
https://github.com/tox-dev/filelock/releases/tag/4.2.1GitHub commit Patch Available
commit 5e3f2ec0c5fb (tox-dev/filelock)
Patch available: tox-dev/filelock 4.2.1 (contains commit 5e3f2ec0c5fb)
https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2dGitHub pull request Patch Available
🐛 fix(read-write): keep SQLite off shared names, bound schema
Patch available: tox-dev/filelock 4.2.1 (PR #834 merged 2026-10-17)
https://github.com/tox-dev/filelock/pull/834GitHub advisoryMentions a patch (unverified)🟡 PoC Available
ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files · Advisory · tox-dev/filelock · GitHub
https://github.com/tox-dev/filelock/security/advisories/GHSA-v4x8-3wr5-3wq8Vendor Advisories for CVE-2026-112940(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| filelock | 3.20.4 ... 4.2.0 (53 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 14× 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 it from the CNA feed. 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). Most recent first.
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-10-25 14:51 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-22 22:26 UTCEG score recompute
- 2026-10-22 21:36 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-21 18:06 UTCEG score recompute
- 2026-10-21 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-20 15:26 UTCEG score recompute
- 2026-10-20 14:48 UTCEG score recomputeFirst assessed: 7.1 HIGH
- 2026-10-20 14:46 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownPyPI:filelock
Frequently asked(5)
What is CVE-2026-112940?
CVE-2026-112940 is a high-severity vulnerability; its CVE record was published on October 20, 2026. filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a…
When was the CVE record for CVE-2026-112940 published?
The CVE record for CVE-2026-112940 was published on October 20, 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 October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-112940 actively exploited?
CVE-2026-112940 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112940?
CVE-2026-112940 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112940?
A fix for CVE-2026-112940 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112940 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-112940
Is Your Infrastructure Affected by CVE-2026-112940?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.