{"answers":{"affected":"3 open source packages ship an affected version, including lemur.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55165 exists.","fix":"Upgrade lemur to 1.9.2 or later.","what":"CVE-2026-55165 is a medium-severity authentication bypass vulnerability in Netflix lemur, published on 18 Aug 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-55165 and fix it if it is affected.\n\nWhat it is: CVE-2026-55165 is a medium-severity authentication bypass vulnerability in Netflix lemur, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55165 exists.\n\nAffected packages and fixed versions:\n- lemur (PyPI): affected all versions; fixed in 1.9.2\n- lemur (PyPI): affected all versions; fixed in 1.9.2\n- lemur (PyPI): affected all versions; fixed in 1.9.2\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-55165/ (Markdown: https://insights.sbomify.com/CVE-2026-55165/index.md)","id":"CVE-2026-55165","markdown":"https://insights.sbomify.com/CVE-2026-55165/index.md","name":"CVE-2026-55165","record":{"aliases":["GHSA-r9gp-7f88-9r54","PYSEC-2026-2589"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"TLS certificate management","requires_auth":"none","summary":"Attackers can bypass JWT authentication in Lemur by manipulating the algorithm header, potentially leading to account takeover if combined with secret disclosure or algorithm confusion.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Lemur manages TLS certificate creation. Prior to 1.9.2, the JWT verifier in lemur/auth/service.py:130-137 used fetch_token_header to read header_data[\"alg\"] from an unverified token and passed that attacker-controlled value to decode_with_multiple_secrets. PyJWT 2.x rejects alg=none with the configured key, so the flaw is a defense-in-depth gap rather than a direct authentication bypass in the shipped configuration. The unpinned algorithm can become exploitable after an asymmetric-signing migration through algorithm confusion, and it weakens algorithm-based anomaly detection because the token chooses the recorded value. A separate disclosure of LEMUR_TOKEN_SECRET would also permit forged HS256 tokens, although that disclosure is an independent prerequisite. The fix introduces the server-controlled LEMUR_TOKEN_ALGORITHMS allowlist and defaults it to HS256. This issue is fixed in version 1.9.2.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Lemur: JWT verifier honors attacker-supplied alg, enabling ATO","id":"CVE-2026-55165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Lemur: ACME SSRF + creator-equality IDOR lead to AWS IAM/PKI compromise","id":"CVE-2026-55166"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.2"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":null,"source":"GHSA-r9gp-7f88-9r54"},{"ecosystem":"PyPI","fixed":["1.9.2"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"GHSA-r9gp-7f88-9r54"},{"ecosystem":"PyPI","fixed":["1.9.2"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"PYSEC-2026-2589"}],"prev":{"headline":"Lemur: Plaintext password storage in Lemur user-update path","id":"CVE-2026-55164"},"products":["lemur"],"published":"2026-08-18","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["Netflix"]},"summary":"Attackers can bypass JWT authentication in Lemur by manipulating the algorithm header, potentially leading to account takeover if combined with secret disclosure or algorithm confusion.","url":"https://insights.sbomify.com/CVE-2026-55165/"}