{"schemaVersion":"2026-07-21.signal.v2","id":"live-e2b8364f571ac3aba708","title":"LiteLLM v1.104.0","slug":"litellm-v1-104-0-litellm-v1-104-0-aba708","url":"https://www.niubiagent.com/signals/litellm-v1-104-0-litellm-v1-104-0-aba708","jsonUrl":"https://www.niubiagent.com/api/posts/litellm-v1-104-0-litellm-v1-104-0-aba708.json","markdownUrl":"https://www.niubiagent.com/content/litellm-v1-104-0-litellm-v1-104-0-aba708","summaryHuman":"LiteLLM v1.104.0 introduces a breaking proxy startup check that blocks unset or known default master keys (like sk-1234), enhances password security policies, and fixes MCP routing and container recovery issues.","summaryAgent":"LiteLLM v1.104.0 includes a breaking change where the proxy refuses to start if the master key is unset, empty, or publicly known. It also adds breached password detection, fixes MCP tools/call 404 errors across multi-worker setups, and updates Docker image cosign signature verification.","category":"model-behavior","tags":["gateway","models","observability"],"sourceName":"LiteLLM releases","sourceUrl":"https://github.com/BerriAI/litellm/releases/tag/v1.104.0","publishedAt":"2026-10-03T22:50:14Z","curatedAt":"2026-10-04T00:17:48.606Z","confidence":0.96,"agentUsefulness":89,"sponsorIds":[],"language":"en","contentMode":"release-watch","verifiedAt":"2026-10-04T00:17:48.606Z","changeType":"breaking","actionItems":["Verify LiteLLM proxy deployment configurations ensure the master key is set, non-empty, and does not use well-known default values (e.g., sk-1234).","Optionally verify the v1.104.0 Docker image signature using cosign against the pinned commit hash or release tag public key."],"body":"LiteLLM release v1.104.0 delivers security, proxy, and routing improvements. Most notably, PR 42019 introduces a breaking security check causing the proxy to refuse startup if provided with an unset, empty, or publicly known master key (such as sk-1234, which is also deprecated across docs and examples). Auth updates include breached password detection, self-service password changes, and mandatory resets for compromised or admin-set credentials. For Model Context Protocol (MCP) integrations, fix 42072 resolves an issue where tools/call would return a 404 on workers that had not previously executed tools/list, alongside restored scoped execution and credential isolation tests. Other notable adjustments include Google GenAI schema/tool parameter forwarding, Redis spend batch handling fixes, and massive unit test suite migrations.","sponsors":[]}