/

CVE-2026-48508

Severity:

HIGH RISK

(8.8)

Authorization Bypass (CWE-863) in Lemur TLS Manager

CVE-2026-48508

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Privilege Escalation and Unauthorized Administrative Actions

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Lemur contains an authorization bypass in permission checks protecting certificate, authority, notification, and domain management actions. When the relevant strict-enforcement settings are not enabled, authenticated read-only users may pass authorization gates and perform administrative operations.

Affected context

The issue occurs in Lemur deployments where ADMIN_ONLY_AUTHORITY_CREATION and LEMUR_STRICT_ROLE_ENFORCEMENT are unset or configured as false. In that state, permission objects may contain no required Need objects, causing Flask-Principal authorization checks to allow any authenticated identity, including users assigned a read-only role.

Exploit preconditions

  • Attack surface: Authenticated Lemur API endpoints for authorities, certificates, notifications, and domains
  • Required access: A valid authenticated account, including an account with read-only privileges
  • Trigger point: A protected API request evaluated through the affected permission classes
  • Why exploitation is possible: Empty permission requirements are treated as automatically satisfied, so the authorization gate does not enforce the intended role or administrative privilege

Why this happens

The underlying bug is an authorization configuration and implementation failure. StrictRolePermission and AuthorityCreatorPermission can initialize Flask-Principal permission objects without any Need objects when their controlling feature flags are false or unset. Because Permission.allows() treats an empty set of requirements as allowed, the application confuses the absence of authorization requirements with a valid authorization decision. This maps to CWE-863: Incorrect Authorization, because access-control checks fail to restrict sensitive operations to appropriately privileged users.

Potential impact

  • Unauthorized users could create root Certificate Authorities
  • Attackers may upload arbitrary certificates
  • Attackers could create or modify notifications that reach an SSRF-capable sink
  • Unauthorized domain entries could be created
  • Certificate-management workflows and trust relationships could be manipulated
  • The application could experience data integrity, confidentiality, or availability impacts

General mitigation guidance

Mitigation generally focuses on making authorization requirements explicit and fail closed.

Common defensive patterns include:

  • Define non-empty permission requirements for every administrative operation
  • Treat unset, disabled, or malformed authorization settings as secure denial rather than unrestricted access
  • Separate read-only and administrative capabilities through explicit role and privilege checks
  • Apply centralized authorization policies consistently across all certificate, authority, notification, and domain endpoints
  • Minimize service-account and user privileges according to least-privilege principles
  • Add authorization tests for each sensitive endpoint using authenticated users with different roles
  • Reduce trust in user-controlled notification destinations and apply SSRF-resistant outbound request controls

How teams detect issues like this

Detection can combine static analysis, code review, runtime monitoring, and policy enforcement:

  • Search for permission constructors or policy objects created with empty requirement collections
  • Review boolean feature flags that alter authorization behavior, especially when false or unset values broaden access
  • Identify authorization checks that default to allow when roles, scopes, or permissions are missing
  • Add regression tests verifying that read-only identities receive denial responses for every administrative endpoint
  • Monitor audit logs for privileged API actions performed by non-administrative roles
  • Enforce API authorization policies in CI and deployment configuration checks
  • Automated code review and security scanning tools may help identify fail-open access-control patterns

Sources

SourceLink
github.comgithub.com/Netflix/lemur/commit/e6a41e2c1b2028840d19039b06895524a19ad36f
github.comgithub.com/Netflix/lemur/releases/tag/v1.9.1
github.comgithub.com/Netflix/lemur/security/advisories/GHSA-qcqw-jwxc-2hqg

Frequently asked

questions

Yes, an authenticated user may be able to exploit the issue through exposed Lemur API endpoints, provided the deployment uses the affected permission behavior.

No. A valid read-only or otherwise lower-privileged authenticated identity may be sufficient when the permission objects contain no required authorization conditions.

Ensure every sensitive operation has explicit, non-empty authorization requirements and that missing or disabled enforcement settings fail closed.

Use centralized role and privilege policies, test every administrative endpoint with lower-privileged accounts, monitor authorization decisions, and prevent configuration changes from weakening access controls.

Find out what's already
exploitable in your codebase.