Incorrect Permission Assignment for Critical Resource Affecting litellm package, versions <1.106.6-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.16% (6th 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-22182466
  • published4 Nov 2026
  • disclosed5 Nov 2026

Introduced: 4 Nov 2026

NewCVE-2026-112910  (opens in a new tab)
CWE-732  (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.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory's inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. This issue is fixed in version 4.2.1.