Description
Lemur manages TLS certificate creation. Prior to 1.9.2, PUT /api/1/roles/ in lemur/roles/views.py:298 authorized updates with RoleMemberPermission(role_id), which allowed either an administrator or any existing member of the target role. The handler passed data["users"] and data["name"] to service.update, allowing a non-admin member to add or remove other users and rename the role. This enabled lateral privilege grants within roles that control certificate and authority access and could deny access by removing legitimate members. The DELETE handler already required admin_permission, confirming that the weaker PUT authorization was inconsistent. The fix applies the same administrator-only requirement to the PUT handler. This issue is fixed in version 1.9.2.
Published: 2026-08-18
Score: 6.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in Lemur’s role update endpoint. The PUT /api/1/roles/<id> endpoint authenticates using RoleMemberPermission, which incorrectly permits any member of the role – not just administrators – to perform updates. The data supplied in the request (the users list and the role name) is forwarded directly to the service layer, allowing a non‑admin member to add or remove users from the role and to rename the role. This bypasses intended role‑based access control and enables a non‑admin member to grant other users additional privileges or revoke legitimate members, thereby achieving lateral privilege escalation and potentially denying legitimate access to certificates and authorities. The flaw is a classic role‑based access control bypass (CWE‑863).

Affected Systems

Vendors: Netflix’s Lemur, a TLS certificate management service. The issue impacts all installations running Lemur versions earlier than 1.9.2. Versions 1.9.2 and newer contain the fix.

Risk and Exploitability

The CVSS score is 6.3, reflecting moderate severity. An attacker needs to be an existing member of the target role, which may be obtained through legitimate credentials or social engineering. Once authenticated, the attacker can install or remove users from a role that controls certificate creation and authority access, effectively escalating privileges or disrupting operations. The EPSS score is not published, and the vulnerability is not listed in the CISA KEV catalog, indicating no known widespread exploitation yet. The attack vector is local or network, requiring authenticated access via the REST API. The mismatch in permission checks renders the exploitation straightforward.

Generated by OpenCVE AI on August 18, 2026 at 20:40 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lemur to version 1.9.2 or later
  • If upgrading is not immediately possible, temporarily block or restrict the PUT /api/1/roles/<id> endpoint to administrators only via configuration
  • Review and audit role memberships to ensure only trusted users are granted membership
  • Enable detailed logging and audit trails for all role modification actions

Generated by OpenCVE AI on August 18, 2026 at 20:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-x3vf-mgxj-7785 Lemur Privilege Escalation: Non-admin role members can rewrite role membership via PUT /api/1/roles/<id>
History

Tue, 18 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Netflix
Netflix lemur
Vendors & Products Netflix
Netflix lemur

Tue, 18 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
Description Lemur manages TLS certificate creation. Prior to 1.9.2, PUT /api/1/roles/ in lemur/roles/views.py:298 authorized updates with RoleMemberPermission(role_id), which allowed either an administrator or any existing member of the target role. The handler passed data["users"] and data["name"] to service.update, allowing a non-admin member to add or remove other users and rename the role. This enabled lateral privilege grants within roles that control certificate and authority access and could deny access by removing legitimate members. The DELETE handler already required admin_permission, confirming that the weaker PUT authorization was inconsistent. The fix applies the same administrator-only requirement to the PUT handler. This issue is fixed in version 1.9.2.
Title Lemur: Privilege escalation via PUT /api/1/roles/<id> — non-admin role members can rewrite role membership
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T18:50:58.130Z

Reserved: 2026-06-16T15:13:28.165Z

Link: CVE-2026-55163

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T19:16:58.357

Modified: 2026-08-18T19:16:58.357

Link: CVE-2026-55163

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T20:45:04Z

Weaknesses