CVE-2026-112913VulnerabilityPublished 29 Oct 2026

lexicon · filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database

Affects lexiconSource GCVE Database

Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 3.25.2_5 when convenient.

Data as of 30 Oct 2026, 07:32 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 3.25.2_5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade lexicon to 3.25.2_5.

Affected software

Product	Affected	Fixed in
Homebrewlexicon`pkg:brew/lexicon`Other threats	Affected >=3.23.2_4 <3.25.2_5	Fixed in 3.25.2_5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in filelock version 3.25.2_5; upgrading to this or later versions resolves the issue. Additionally, ensure that lock directories on Windows are not writable by untrusted users who should not have delete permissions on the lock user's files. The filelock documentation advises that the lock directory must not be writable by untrusted users to prevent such issues. No other specific mitigations are indicated.

Description

On Windows, the filelock library's ReadWriteLock and AsyncReadWriteLock use SQLite side files for locking. A local user who can create files but not delete others' files in the lock directory can place a specially crafted side file (e.g., -wal or -journal) beside the database. This causes the lock user to encounter disk I/O errors or unexpected file deletions during lock acquisition, resulting in partial denial of service. The issue affects filelock versions 3.20.4 through 4.2.0 on Windows. A fix is available in version 3.25.2_5.

Impact

The vulnerability allows a local user with create-but-not-delete permissions in the lock directory to cause denial of service for the lock user by placing a side file that triggers sqlite3.OperationalError exceptions on every lock acquisition attempt. This prevents the lock user from successfully acquiring read or write locks until the file is removed by the attacker. There is no confidentiality or broad integrity impact in the common variant. A deletion variant can cause the lock user's process to delete one of its own files, causing limited integrity impact. The overall impact is partial availability loss for the lock user on Windows systems where the directory permissions allow such file creation by other users.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 07:32 UTC

Technical details

References

Community reviews

Related threats