Quick answers
- Is CVE-2026-114612 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114612 being exploited in the wild.
- How severe is CVE-2026-114612?
- Critical severity, with a CVSS score of 9.9, published 22 October 2026.
- Which products and versions are affected?
- Berriai LiteLLM 1.87.0 to 1.100.3, 1.101.2, 1.102.1, 1.103.0; litellm (PyPI) >= 1.91.0, < 1.100.4, ECOSYSTEM:introduced=1.91.0,fixed=1.100.4.
- Is there a fix for CVE-2026-114612?
- Yes. litellm (PyPI): upgrade to 1.100.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114612 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-114612?
- Check whether you run Berriai LiteLLM or litellm (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- litellm (PyPI): upgrade to 1.100.4 or later
pip install "litellm>=1.100.4"
Technical details
The vulnerability exists in the cryptographic context handling for authentication tokens. Versions 1.87.0 through 1.100.3, 1.101.2, 1.102.1, and 1.103.0 reuse a single AES-GCM encryption context for both API-key flow secrets and UI/CLI session tokens, allowing an authenticated internal user to craft a forged administrator credential, encrypt it using the secret flow, and replay the ciphertext as a bearer token to gain unauthorized administrative access to the MCP stdio endpoint. The issue affects default configurations in versions 1.91.0 and later.
Affected products
- BerriAI LiteLLM 1.87.0 to 1.100.3, 1.101.2, 1.102.1, 1.103.0
Identifiers
- CVE-2026-114612
- GHSA-7hp6-4w63-5g45
Timeline
- 2026-10-22: disclosed