NVD / CVE Program· CNA GitHub_M

CVE-2026-71417: Lemur: Any user can revoke arbitrary certificates at the CA by uploading a duplicate record and revoking it

HighCVSS 7.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Netflix lemur 1.9.3.

Low priority for now. Upgrade to Netflix lemur 1.9.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/certificates/upload allowed a non-read-only user to create a duplicate row using another certificate body, authority_id, serial, or external_id without requiring permission on the underlying authority. PUT /api/1/certificates//revoke authorized the caller against only the selected Lemur row, so the creator of the duplicate bypassed CertificatePermission. The duplicate had no cert.endpoints, which also bypassed the safeguard that prevents revocation of deployed certificates. Issuer plugins then revoked the real CA-side certificate using certificate.body or external_id under the stored authority credentials. An attacker could therefore revoke arbitrary managed certificates and cause fleet-wide TLS denial of service. The fix rejects duplicate authority_id and serial identities, requires authority access on upload, and checks every matching row during revocation. This issue is fixed in version 1.9.3.

Broken access control (IDOR)

Published: Aug 18, 2026
Updated: Oct 22, 2026
EPSS: 0.1% · 1th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.3; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

Netflix lemur
- < 1.9.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
PyPI	lemur	before 1.9.3	1.9.3

Same product

netflix: all records

Other highest-scoring records for the same primary product.

CVE-2026-55166Lemur: any SSO-authenticated user achieves AWS IAM compromise and permanent PKI key access via ACME acme_url SSRF and creator-equality IDOR
39Monitor
CVE-2026-48508Lemur: Authorization bypass in StrictRolePermission / AuthorityCreatorPermission
35Monitor
CVE-2026-71308Lemur: Unchecked `replaces[]` lets any user silence notifications and hijack auto-rotation for arbitrary certificates
32Monitor

Published before and after this one in the same product

← EarlierCVE-2026-71307Aug 18, 2026 · Lemur: Authenticated low-privilege users can read plaintext destination credentials (SFTP password / private-key passphrase) via the destinations API
30Monitor
← EarlierCVE-2026-71317Aug 18, 2026 · Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority
26Monitor
← EarlierCVE-2026-71322Aug 18, 2026 · Lemur: Missing authorization check on POST /certificates/<id>/export for plugins with requires_key = False
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Netflix lemur	1.9.3 · description	Vendor (CNA)
PyPI:lemur	1.9.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Netflix/lemurcommit 851389a

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-713080 days apartLemur: Unchecked `replaces[]` lets any user silence notifications and hijack auto-rotation for arbitrary certificates
32Monitor

Bug bounty scope

NetflixHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: researcher credit.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Changed
Confidentiality impact: None
Integrity impact: Low
Availability impact: High

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/Netflix/lemur/commit/851389ae737a6d6bf16c1f9ca64a2ce56c1cc5c6

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records