NPM · SEPTEMBER 2026 · EARLY WARNING

LightLLM Remote Code Execution Vulnerability: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
CRITICAL
CVSS
9.8
Affected component
litellm (npm)
Affected versions
>= v1.2.0, <= v1.2.0 or >= v1.1.0, <= v1.1.0 or >= v1.0.1, <= v1.0.1 or >= v1.0.0, <= v1.0.0
Patched version
Not yet available
CVE-2026-90919

LightLLM through version 1.2.0 reportedly contains a remote code execution vulnerability. Users of affected versions should take immediate action.

What happened

LightLLM through version 1.2.0 appears to contain a critical remote code execution vulnerability in the Config Server's unauthenticated /visual_register WebSocket endpoint. This vulnerability allows attackers to send a malicious serialized payload with a __reduce__ method to execute arbitrary code with Config Server process privileges. The vulnerability is tracked as CVE-2026-90919 with a CVSS score of 9.8.

The vulnerability was first flagged on September 14, 2026. It is not yet confirmed to be exploited in the wild. The affected components include litellm (npm) in versions >= v1.2.0, <= v1.2.0 or >= v1.1.0, <= v1.1.0 or >= v1.0.1, <= v1.0.1 or >= v1.0.0, <= v1.0.0.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If litellm is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using litellm (npm) in versions >= v1.2.0, <= v1.2.0 or >= v1.1.0, <= v1.1.0 or >= v1.0.1, <= v1.0.1 or >= v1.0.0, <= v1.0.0.

What should I do right now?

Upgrade to a version of LightLLM beyond 1.2.0 and review any potential unauthorized access to the Config Server.

Is there an official fix available?

No official fix has been published yet. Monitor the primary sources for updates.

Sources

Join the 0Day waitlist →

← Back to all threats