{"answers":{"affected":"3 open source packages ship an affected version, including lemur.","exploited":"There is no known exploitation of CVE-2026-71322 in the wild and no public exploit code.","fix":"Upgrade lemur to 1.9.3 or later.","what":"CVE-2026-71322 is a medium-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-71322 and fix it if it is affected.\n\nWhat it is: CVE-2026-71322 is a medium-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: There is no known exploitation of CVE-2026-71322 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lemur (PyPI): affected all versions; fixed in 1.9.3\n- lemur (PyPI): affected all versions; fixed in 1.9.3\n- lemur (PyPI): affected all versions; 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-71322/ (Markdown: https://insights.sbomify.com/CVE-2026-71322/index.md)","id":"CVE-2026-71322","markdown":"https://insights.sbomify.com/CVE-2026-71322/index.md","name":"CVE-2026-71322","record":{"aliases":["GHSA-4h97-p9wq-chqj","PYSEC-2026-3673"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Certificate management tool","requires_auth":"low_privilege","summary":"Attackers can bypass ownership checks to export certificates via plugins that do not require private keys, potentially exposing public certificate data and corrupting audit logs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Lemur manages TLS certificate creation. Prior to 1.9.3, CertificateExport placed its CertificatePermission ownership check inside the plugin.requires_key branch for POST /api/1/certificates//export. A plugin declaring requires_key false bypassed that check, and the handler still passed cert.private_key as an argument and recorded a key_view audit event. The bundled JavaTruststoreExportPlugin ignored the key, so the immediate exposure was limited to public certificate material and misleading audit entries, but a future plugin could have consumed the supplied key. The fix passes no private key to plugins that do not require one and confines ownership checks and key_view logging to actual private-key exports. 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":"none_known"},"has_fix":true,"headline":"Lemur: Missing authorization check on POST /certificates/\u003cid\u003e/export for plugins with requires_key = False","id":"CVE-2026-71322","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":"Traefik: Cross-user response poisoning via proxied CONNECT on Traefik's shared backend keep-alive pool","id":"CVE-2026-71324"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":null,"source":"GHSA-4h97-p9wq-chqj"},{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"GHSA-4h97-p9wq-chqj"},{"ecosystem":"PyPI","fixed":["1.9.3"],"introduced":["0"],"last_affected":[],"package":"lemur","purl":"pkg:pypi/lemur","source":"PYSEC-2026-3673"}],"prev":{"headline":"Nuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validation","id":"CVE-2026-71321"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["Netflix"]},"summary":"Attackers can bypass ownership checks to export certificates via plugins that do not require private keys, potentially exposing public certificate data and corrupting audit logs.","url":"https://insights.sbomify.com/CVE-2026-71322/"}