CVE-2026-55163Medium· 6.3▾ SunlitLemur 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.…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 34.7 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
0.2%
Last analysed / modified upstream
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.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Affected packages:
lemur <= 1.9.1Patched in:
lemur 1.9.2Connected by shared product, vendor, weakness, or advisory.
CVE-2026-48508High· 8.8Lemur manages TLS certificate creation
CVE-2026-55162Medium· 6.3Lemur manages TLS certificate creation
CVE-2026-55164Medium· 4.9Lemur manages TLS certificate creation
CVE-2026-55165Medium· 4.8Lemur manages TLS certificate creation
CVE-2026-55166Critical· 9.9Lemur manages TLS certificate creation
CVE-2015-7764High· 7.5Lemur uses static IV per key