Lemur Privilege Escalation: Non-admin role members can rewrite role membership via PUT /api/1/roles/<id> (CVE-2026-55163)
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.
AI Analysis
Technical Summary
Lemur, a TLS certificate management tool, had a vulnerability (CVE-2026-55163) in versions before 1.9.2 where the PUT /api/1/roles/<id> endpoint authorized updates based on membership in the target role rather than requiring administrator privileges. This allowed any non-admin member of a role to add or remove users from that role and rename it, enabling lateral privilege escalation and potential denial of access to legitimate members. The DELETE handler already required admin permissions, so the PUT handler's weaker authorization was inconsistent. The vulnerability is fixed in version 1.9.2 by enforcing administrator-only access for the PUT handler.
Potential Impact
An attacker who is a non-admin member of a role can escalate privileges by modifying role membership and renaming roles that control certificate and authority access. This could lead to unauthorized access to TLS certificates or denial of access to legitimate users. The vulnerability has a CVSS 3.1 score of 6.3 (medium severity), indicating a moderate impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Lemur to version 1.9.2 or later, where the PUT /api/1/roles/<id> endpoint requires administrator privileges to update roles. This official fix corrects the authorization flaw and prevents non-admin users from modifying role membership or names.
Lemur Privilege Escalation: Non-admin role members can rewrite role membership via PUT /api/1/roles/<id> (CVE-2026-55163)
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.
CVSS v3.1
Score 6.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Lemur, a TLS certificate management tool, had a vulnerability (CVE-2026-55163) in versions before 1.9.2 where the PUT /api/1/roles/<id> endpoint authorized updates based on membership in the target role rather than requiring administrator privileges. This allowed any non-admin member of a role to add or remove users from that role and rename it, enabling lateral privilege escalation and potential denial of access to legitimate members. The DELETE handler already required admin permissions, so the PUT handler's weaker authorization was inconsistent. The vulnerability is fixed in version 1.9.2 by enforcing administrator-only access for the PUT handler.
Potential Impact
An attacker who is a non-admin member of a role can escalate privileges by modifying role membership and renaming roles that control certificate and authority access. This could lead to unauthorized access to TLS certificates or denial of access to legitimate users. The vulnerability has a CVSS 3.1 score of 6.3 (medium severity), indicating a moderate impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Lemur to version 1.9.2 or later, where the PUT /api/1/roles/<id> endpoint requires administrator privileges to update roles. This official fix corrects the authorization flaw and prevents non-admin users from modifying role membership or names.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-x3vf-mgxj-7785
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-55163"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a3ef7e527e9c79719032b4b
Added to database: 06/26/2026, 22:06:29 UTC
Last enriched: 08/19/2026, 11:15:39 UTC
Last updated: 09/15/2026, 01:32:09 UTC
Views: 133
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.