CVE-2026-112938

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.8 from GitHub Security Advisory (severity: MODERATE) published 2026-10-28. A secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-117814 (ENISA EUVD) · GHSA-m462-7rxw-wvpg (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1.

CVSS v3
5.8
EG Score
5.8MEDIUMhigh confidence
EG Risk
26
EG Risk 26/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)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-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-10). 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 every mission impact level.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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (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 28, 2026

Last Modified

November 9, 2026

Advisory Details (5)

Auto-updated Nov 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses · Advisory · tox-dev/filelock · GitHub

Affected: 4.0.9). There the other user chose the file the lock opened. Here the link sits o

https://github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg
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.1
GitHub pull request Patch Available

🐛 fix(strict): keep claim directories private to the lock

Patch available: tox-dev/filelock 4.2.1 (PR #839 merged 2026-10-17)

https://github.com/tox-dev/filelock/pull/839
GitHub commit Patch Available

commit bfa066d65a1b (tox-dev/filelock)

Patch available: tox-dev/filelock 4.2.1 (contains commit bfa066d65a1b)

https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
GitHub commit

commit aaa18595d297 (tox-dev/filelock)

Fix landed in tox-dev/filelock commit aaa18595d297 — awaiting tagged release

https://github.com/tox-dev/filelock/commit/aaa18595d29795fab599a69d6b184d9a505dab4b

Vendor Advisories for CVE-2026-112938(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 / EcosystemFix (by version range) / PatchReleasedSource
pipfilelock @ 4.2.1 (fixes >= 3.30.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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-filelock3.12.2-1 ... 4.2.8-1 (35 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-filelock3.18.0-1 ... 4.2.8-1 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-filelock3.18.0-1 ... 4.1.1-1 (21 versions)
  • every version up to 4.2.2-1: fixed in 4.2.2-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
filelock3.30.0 ... 4.2.0 (31 versions)
  • 3.30.0 up to 4.2.1: fixed in 4.2.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 15× 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.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-11-11 06:44 UTCEchelonGraph re-scored
  5. 2026-11-11 06:44 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-11-09 18:27 UTCEchelonGraph re-scored
  8. 2026-11-09 18:27 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  9. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-11-06 21:48 UTCEchelonGraph re-scored
  13. 2026-11-06 21:48 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  14. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-11-05 23:12 UTCENISA EUVD ID recordedEUVD-2026-117814 · Source: ENISA EUVD
  16. 2026-11-05 22:30 UTCEchelonGraph re-scored
  17. 2026-11-05 22:30 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  18. 2026-11-05 21:58 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  19. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-m462-7rxw-wvpg · GitHub severity MODERATE · GitHub CVSS 5.8
  20. 2026-11-01 07:59 UTCEchelonGraph re-scored
  21. 2026-10-28 21:39 UTCEchelonGraph re-scoredFirst assessed: 5.8 MEDIUM

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-112938?
CVE-2026-112938 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a…
When was the CVE record for CVE-2026-112938 published?
The CVE record for CVE-2026-112938 was published on October 28, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-112938 actively exploited?
CVE-2026-112938 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-112938?
CVE-2026-112938 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112938?
A fix for CVE-2026-112938 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112938 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-112938

Explore →

Is Your Infrastructure Affected by CVE-2026-112938?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs