Nearly 1 in 10 Exposed LiteLLM Gateways Accepted Example Admin Key sk-1234

The Hacker News reported on September 10, 2026 that Wiz Research’s February scan of 3,074 LiteLLM gateways visible on Shodan found 294 that still accepted sk-1234, the example admin key printed in LiteLLM’s own setup guide. In 191 of those cases no master key was set at all, so any value would have worked. As of September 9, THN notes, the setup guide still showed the example string above a comment telling operators to replace it before production use.

LiteLLM is an open-source AI gateway that sits between applications and paid model providers. Wiz argues the master key matters because it is both the administrator credential and the switch that enables authentication. Before 1.82.0-stable, a gateway started without a master key granted every caller full admin rights. An admin can read stored provider API keys, inspect prompts and replies, reach configured MCP tools, and—in Wiz’s demonstration—abuse pass-through routes toward cloud instance metadata. LiteLLM treats some setup mistakes as out of scope for CVE assignment; there is no CVE for the pass-through metadata path itself.

Related flaws already under active abuse

THN separates the default-key finding from older LiteLLM issues that are already being exploited. CISA added CVE-2026-59822 (MCP authentication bypass via arbitrary Bearer tokens) to its Known Exploited Vulnerabilities catalog on September 2, with a federal remediation date of September 16; it is fixed in 1.84.0. CVE-2026-42271, chained with Starlette host-header CVE-2026-48710, has been used to run commands and steal keys—Microsoft’s August case urged treating AI gateways as Tier-0 secrets stores. Wiz also tracked guardrail code-execution issues CVE-2026-59821 and CVE-2026-40217, fixed earlier in 2026.

Operators should rotate any default or empty master key to a long random value, upgrade to 1.84.0 or later, and tighten network and IAM exposure. This brief summarizes public reporting only and does not include exploit procedures.

Primary source is The Hacker News’ September 10 summary of the Wiz research and related CVE timeline.