Time-of-check Time-of-use (TOCTOU) Affecting litellm package, versions <1.106.6-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.12% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-LITELLM-22182428
  • published4 Nov 2026
  • disclosed5 Nov 2026

Introduced: 4 Nov 2026

NewCVE-2026-112913  (opens in a new tab)
CWE-367  (opens in a new tab)

How to fix?

Upgrade Chainguard litellm to version 1.106.6-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream litellm package and not the litellm package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.