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.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-22182412
  • published4 Nov 2026
  • disclosed5 Nov 2026

Introduced: 4 Nov 2026

NewCVE-2026-112908  (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 version 3.30.0 until version 4.2.1,  StrictSoftFileLock  and  AsyncStrictSoftFileLock  on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1.

CVSS Base Scores

version 3.1