CVE-2026-112913 tox-dev CVE debrief

Who should care

Defenders responsible for securing Windows systems and applications using the filelock package should assess exposure and apply the patch to prevent local denial of service attacks.

Why it matters

The vulnerability in the filelock package allows a local user to create a denial of service for other local users, potentially leading to privilege escalation and data corruption or loss. Defenders should prioritize verifying the package version and applying the patch.

• Denial of service for local users
• Potential for privilege escalation
• Increased risk of data corruption or loss

Technical summary

The filelock package uses SQLite to implement reader/writer locks on Windows. However, SQLite acts on side files beside the database before acquiring the lock, allowing a local user to create a side file and deny others from deleting it, causing a denial of service. This issue arises from the way SQLite handles side files, which are derived from the database path and include files such as `<database>-journal`, `<database>-wal`, and `<database>-shm`. A local user can exploit this vulnerability by creating one of these side files in a directory where the database is located.

Defensive priority

Defenders should prioritize verifying the filelock package version and applying the patch to prevent local denial of service attacks.

Recommended defensive actions

• Verify the filelock package version and upgrade to 4.2.1 or later
• Review and update access controls to prevent local users from creating files in sensitive directories
• Monitor for suspicious activity related to SQLite databases and side files
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The issue is caused by the way SQLite handles side files beside the database. A local user can create a side file and deny others from deleting it, causing a denial of service. This is possible because SQLite acts on these side files before acquiring the lock. The side files in question are derived from the database path and include files such as `<database>-journal`, `<database>-wal`, and `<database>-shm`. An attacker can exploit this by creating one of these files in a directory where the database is located, which can lead to a `磁盘

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.