Skip to main content
VulnerabilityPublished

CVE-2026-71308: Netflix lemur · Insecure Direct Object Reference

Affects Netflix lemurSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 1.9.3 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
NetflixlemurAffected
  • >=0.5.0 <1.9.3
Fixed in
  • 1.9.3
GitHubnetflix/lemurpkg:github/netflix/lemurOther threatsAffected
  • <1.9.3 >=0.5.0
Fixed in
  • 1.9.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Lemur to version 1.9.3 or later, where authorization checks on replacement certificates are enforced before mutation. Since this is an on-premises product, apply the official fix promptly to prevent exploitation. Patch status is confirmed fixed in version 1.9.3.

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.

References

Community reviews

Loading reviews…