LiteLLM authentication bypass and password hash exposure
LiteLLM
LiteLLM stored passwords using weak unsalted SHA-256 hashes and exposed them in API responses to authenticated users. This flaw enabled a pass-the-hash authentication bypass attack against the login endpoint.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- fix status
- Fix status unknown
- first report
- 8 Apr 2026
- last update
- 8 Apr 2026
Timeline · 1
Sources · 1
Advisories and databases
- 2026-04-08GHSA-69x8-hrgq-fjj8: LiteLLM: Password hash exposure and pass-the-hash authentication bypassGitHub Advisory Database · github.com/advisories/GHSA-69x8-hrgq-fjj8
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 8 Apr 2026 · first reported 8 Apr 2026
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 10:14Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# LiteLLM authentication bypass and password hash exposure https://gcdradar.vercel.app/incidents/ghsa-69x8-hrgq-fjj8-litellm-authentication-bypass-and-passwo · AIR-2026-0561 · closed 2026-04-08 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-04-08 - AI role: Attack on AI - Products: LiteLLM ## Summary LiteLLM stored passwords using weak unsalted SHA-256 hashes and exposed them in API responses to authenticated users. This flaw enabled a pass-the-hash authentication bypass attack against the login endpoint. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-04-08: GHSA-69x8-hrgq-fjj8: LiteLLM: Password hash exposure and pass-the-hash authentication bypass (https://github.com/advisories/GHSA-69x8-hrgq-fjj8) ## Sources - 2026-04-08 GitHub Advisory Database: GHSA-69x8-hrgq-fjj8: LiteLLM: Password hash exposure and pass-the-hash authentication bypass https://github.com/advisories/GHSA-69x8-hrgq-fjj8 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.8LiteLLM CVE-2026-42271: LiteLLM Authenticated Command Execution via MCP Endpoints
Patch now · Disclosed · since 25 Apr 2026 · updated 8 May 2026 · CVE-2026-42271
AI - closed8.6LiteLLM CVE-2026-42203: LiteLLM Server-Side Template Injection
Patch now · Disclosed · since 24 Apr 2026 · updated 8 May 2026 · CVE-2026-42203
AI - closed9.8LiteLLM CVE-2026-42208: LiteLLM proxy API key verification SQL injection
Patch now · Disclosed · since 24 Apr 2026 · updated 8 May 2026 · CVE-2026-42208
AI - closed8.8LiteLLM CVE-2026-40217: LiteLLM sandbox escape in custom-code guardrail
Patch now · Disclosed · since 11 May 2026 · updated 11 May 2026 · CVE-2026-40217
AI - closedLiteLLM LiteLLM sandbox escape vulnerability in custom-code guardrail
Patch now · Disclosed · since 10 Apr 2026
AI - closed9.4LiteLLM CVE-2026-35030: LiteLLM authentication bypass via OIDC cache collision
Patch now · Disclosed · since 3 Apr 2026 · updated 6 Apr 2026 · CVE-2026-35030
AI