{"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-71308 exists.","fix":"Upgrade lemur to 1.9.3 or later.","what":"CVE-2026-71308 is a high-severity missing authorization vulnerability in Netflix lemur, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71308 and fix it if it is affected.\n\nWhat it is: CVE-2026-71308 is a high-severity missing authorization vulnerability in Netflix lemur, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71308 exists.\n\nAffected packages and fixed versions:\n- lemur (PyPI): affected from 0.5.0; fixed in 1.9.3\n- lemur (PyPI): affected from 0.5.0; fixed in 1.9.3\n- lemur (PyPI): affected from 0.5.0; fixed in 1.9.3\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-71308/ (Markdown: https://insights.sbomify.com/CVE-2026-71308/index.md)","id":"CVE-2026-71308","markdown":"https://insights.sbomify.com/CVE-2026-71308/index.md","name":"CVE-2026-71308","record":{"aliases":["GHSA-cfh6-pv5c-38jv","PYSEC-2026-3675"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TLS certificate management","requires_auth":"low_privilege","summary":"Authenticated users can hijack certificate rotation and suppress notifications for arbitrary certificates due to missing permission checks on replacement objects.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Lemur manages TLS certificate creation. From 0.5.0 until 1.9.3, certificate create, upload, and edit requests accepted replaces[] or replacements identifiers that AssociatedCertificateSchema resolved with fetch_objects without a CertificatePermission check. Assigning those objects to Certificate.replaces invoked an append listener that disabled the victim certificate notifications and marked it as replaced. The victim was then excluded from get_all_pending_reissue, and certificate_rotate could deploy the attacker certificate to endpoints serving the victim. An authenticated non-read-only user could target certificates for which the user had no ownership or role, suppress lifecycle automation, and cause fleet-wide TLS disruption or unauthorized substitution. The fix authorizes every referenced replacement certificate before mutation. This issue is fixed in version 1.9.3.","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: Unchecked `replaces[]` lets any user silence notifications and hijack auto-rotation for arbitrary certificates","id":"CVE-2026-71308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"rclone: Incomplete path validation allows backend root escape in serve restic","id":"CVE-2026-71309"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0.5.0"],"last_affected":[],"package":"lemur","purl":null,"source":"GHSA-cfh6-pv5c-38jv"},{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0.5.0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"GHSA-cfh6-pv5c-38jv"},{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0.5.0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"PYSEC-2026-3675"}],"prev":{"headline":"Lemur: Authenticated low-privilege users can read plaintext destination credentials (SFTP password / private-key passphrase) via the destinations API","id":"CVE-2026-71307"},"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":"Authenticated users can hijack certificate rotation and suppress notifications for arbitrary certificates due to missing permission checks on replacement objects.","url":"https://insights.sbomify.com/CVE-2026-71308/"}