LiteLLM 1.107.0 compromise turns AI gateway updates into incident…PHP2Shell patches close unauthenticated RCE across web-serving PHPRailway secret-store incident forces credential rotation…eMudhra cleanup expands from eight intermediate keys to root-store…
Thursday, 22 October 2026 · Executive decision brief
LiteLLM 1.107.0 compromise turns AI gateway updates into incident response
A compromised release pipeline distributed a credential stealer and remote-code loader through LiteLLM 1.107.0 wheels and official container tags.
Security.io Intelligence Desk · Thursday, 22 October 2026
Executive consequence
Assume compromise wherever LiteLLM 1.107.0 executed. Isolate and rebuild those environments, hunt the published artefacts and infrastructure, and rotate every credential the host or container could access.
Decision today
Quarantine every host or container that executed LiteLLM 1.107.0.
Deploy PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, isolate systems that cannot be fixed, and investigate exposed services separately from confirming patch status.
Do today
Deploy PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 across supported branches.
Rotate secrets stored in Railway, review every downstream service they unlock, preserve audit evidence and plan around the temporary inability to deploy new application versions.
Do today
Rotate high-privilege secrets stored in Railway environment variables.
Update browser and non-browser trust stores, identify services chaining to the affected eMudhra hierarchy, and prove both fraudulent-chain rejection and legitimate-service continuity.
Do today
Update affected browser, operating-system, language and application trust stores.
TAKKT customers and business partners should assess fulfilment dependencies, activate alternate processes and monitor for data-impact or restoration disclosures before relying on normal delivery assumptions.
Do today
Map orders, deliveries and customer commitments dependent on affected TAKKT operations.