CVE-2026-71322: Netflix lemur · Missing Authorization
Affects Netflix lemurSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.9.3 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade lemur and netflix/lemur to 1.9.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Netflixlemur | Affected
| Fixed in
|
GitHubnetflix/lemurpkg:github/netflix/lemurOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Lemur version 1.9.3 or later, where this issue is fixed. The fix prevents private key data from being passed to plugins that do not require it and enforces ownership checks and audit logging only for actual private key exports.
Description
CVE-2026-71322 is a medium severity vulnerability in Netflix's Lemur prior to version 1.9.3. It involves missing authorization checks in the CertificateExport functionality, where plugins that do not require a private key could bypass ownership verification and receive private key data unnecessarily. The immediate impact was limited to exposure of public certificate material and misleading audit logs, but future plugins could potentially misuse the private key. The issue is fixed in Lemur version 1.9.3 by restricting private key access and ownership checks to relevant plugins only.