{"answers":{"affected":"3 open source packages ship an affected version, including litellm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35030 in the wild and no public exploit code.","fix":"Upgrade litellm to 1.83.0 or later.","what":"CVE-2026-35030 is a critical authentication bypass vulnerability in BerriAI litellm, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35030 and fix it if it is affected.\n\nWhat it is: CVE-2026-35030 is a critical authentication bypass vulnerability in BerriAI litellm, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35030 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- litellm (PyPI): affected all versions; fixed in 1.83.0\n- litellm (PyPI): affected all versions; fixed in 1.83.0\n- litellm (PyPI): affected all versions; fixed in 1.83.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-35030/ (Markdown: https://insights.sbomify.com/CVE-2026-35030/index.md)","id":"CVE-2026-35030","markdown":"https://insights.sbomify.com/CVE-2026-35030/index.md","name":"CVE-2026-35030","record":{"aliases":["CLEANSTART-2026-JK38146","GHSA-jjhc-v7c2-5hh6","MINI-975h-r96j-7xm6","MINI-gc87-9qh7-xh7p","MINI-gv7r-cjh8-p958","MINI-wjjm-x2wv-75pw","MINI-xr28-j2m8-h74x","PYSEC-2026-390"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"AI Gateway Proxy","requires_auth":"none","summary":"An attacker can bypass authentication and impersonate users by exploiting OIDC cache key collisions in LiteLLM when JWT authentication is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"litellm","vendor":"litellm"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-222","name":"Truncation of Security-relevant Information"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, when JWT authentication is enabled (enable_jwt_auth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters. This configuration option is not enabled by default. Most instances are not affected. An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user's cached token. On cache hit, the attacker inherits the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled. Fixed in v1.83.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-05-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-19T12:13:16Z","kind":"github_poc","ref":"https://github.com/learner202649/CVE-2026-35030-PoC","stars":0,"title":"The code for personally reproducing the corresponding vulnerability"}],"tier":"poc_unverified"},"has_fix":true,"headline":"LiteLLM has an authentication bypass via OIDC userinfo cache key collision","id":"CVE-2026-35030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain","id":"CVE-2026-35031"},"packages":[{"ecosystem":"PyPI","fixed":["1.83.0"],"introduced":["0"],"last_affected":[],"package":"litellm","purl":null,"source":"GHSA-jjhc-v7c2-5hh6"},{"ecosystem":"PyPI","fixed":["1.83.0"],"introduced":["0"],"last_affected":[],"package":"litellm","purl":"pkg:pypi/litellm","source":"GHSA-jjhc-v7c2-5hh6"},{"ecosystem":"PyPI","fixed":["1.83.0"],"introduced":["0"],"last_affected":[],"package":"litellm","purl":"pkg:pypi/litellm","source":"PYSEC-2026-390"}],"prev":{"headline":"LiteLLM affected by privilege escalation via unrestricted proxy configuration endpoint","id":"CVE-2026-35029"},"products":["litellm"],"published":"2026-04-06","related":[{"cvss_score":9.3,"headline":"BerriAI LiteLLM SQL Injection","id":"CVE-2026-42208","kev_date_added":"2026-05-08","published":"2026-05-08"},{"cvss_score":8.8,"headline":"BerriAI LiteLLM Improper Authentication","id":"CVE-2026-59822","kev_date_added":"2026-09-02","published":"2026-07-08"},{"cvss_score":8.7,"headline":"BerriAI LiteLLM Command Injection","id":"CVE-2026-42271","kev_date_added":"2026-06-08","published":"2026-05-08"},{"cvss_score":9.8,"headline":"Remote Code Execution in BerriAI/litellm","id":"CVE-2024-5751","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":9.8,"headline":"Server-Side Template Injection in BerriAI/litellm","id":"CVE-2024-2952","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"LiteLLM: Authentication Bypass via Host Header Injection","id":"CVE-2026-49468","kev_date_added":null,"published":"2026-06-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["BerriAI"]},"summary":"An attacker can bypass authentication and impersonate users by exploiting OIDC cache key collisions in LiteLLM when JWT authentication is enabled.","url":"https://insights.sbomify.com/CVE-2026-35030/"}