How severe is CVE-2026-112906?

CVE-2026-112906 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-112906 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-112906?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-112906 published?

CVE-2026-112906 was published on 2026-10-20.

CVE-2026-112906

CVE-2026-112906 is a medium-severity vulnerability with a CVSS 3.x base score of 4.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-694.

Key facts

Severity: Medium (CVSS 3.x base score 4.7)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-694
Published: 2026-10-20
Last modified: 2026-10-20

Description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.

Frequently asked questions

What is CVE-2026-112906?: filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.
How severe is CVE-2026-112906?: CVE-2026-112906 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-112906 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-112906?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-112906 published?: CVE-2026-112906 was published on 2026-10-20.

References

Other CWE-694 vulnerabilities

CVE-2026-63976 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: clear chan->ident on ECRED…
CVE-2025-13609 — High (CVSS 8.2): A vulnerability has been identified in keylime where an attacker can exploit this flaw by registering a new agent using…
CVE-2026-71327 — High (CVSS 8.1): Traefik is an open source HTTP reverse proxy and load balancer. From 3.0.0 until 3.6.25 and 3.7.10, Traefik's…
CVE-2025-59048 — High (CVSS 8.1): OpenBao's AWS Plugin generates AWS access credentials based on IAM policies. Prior to version 0.1.1, the AWS Plugin is…
CVE-2026-102634 — High (CVSS 7.5): SGLang through 0.5.20 in prefill/decode disaggregation mode fails to validate duplicate bootstrap_room fields in…
CVE-2023-20100 — Medium (CVSS 6.8): A vulnerability in the access point (AP) joining process of the Control and Provisioning of Wireless Access Points…

Browse all CWE-694 vulnerabilities →