Skip to main content
VulnerabilityPublished

CVE-2026-48508: Netflix lemur · Incorrect Authorization

Affects Netflix lemurSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 1.9.1 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.9.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 15 Nov 2026.

What to do

Upgrade lemur and netflix/lemur to 1.9.1.

Affected software

ProductAffectedFixed in
NetflixlemurAffected
  • <1.9.1
Fixed in
  • 1.9.1
GitHubnetflix/lemurpkg:github/netflix/lemurOther threatsAffected
  • <1.9.1
Fixed in
  • 1.9.1

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.1 or later, where this authorization issue is fixed. Explicitly setting ADMIN_ONLY_AUTHORITY_CREATION or LEMUR_STRICT_ROLE_ENFORCEMENT to True also mitigates the permissive authorization behavior. Patch status is not explicitly stated but the fix is available in version 1.9.1.

Description

Lemur manages TLS certificate creation. Prior to 1.9.1, StrictRolePermission and AuthorityCreatorPermission in lemur/auth/permissions.py call flask_principal.Permission.__init__() with zero Need objects when ADMIN_ONLY_AUTHORITY_CREATION and LEMUR_STRICT_ROLE_ENFORCEMENT are unset because both flags default to False. Flask-Principal Permission.allows() returns True when self.needs is empty, so the .can() authorization gate permits every authenticated identity, including the read-only role. A read-only user can access POST /api/1/authorities, POST /api/1/certificates/upload, POST /api/1/pending_certificates//upload, POST /api/1/notifications, PUT or DELETE /api/1/notifications/, and POST /api/1/domains to create root Certificate Authorities, upload arbitrary certificates, create or edit notifications that reach an SSRF sink, and create domain entries. Explicitly setting either flag to False continues to opt into the permissive behavior. This issue is fixed in version 1.9.1.

References

Community reviews

Loading reviews…