PT-2026-52643 · Lemur · Lemur
CVE-2026-48508
·
Published
2026-06-25
·
Updated
2026-08-18
CVSS v3.1
8.8
High
| Vector | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Name of the Vulnerable Software and Affected Versions
Lemur versions prior to 1.9.1
Description
An authorization bypass exists in
StrictRolePermission and AuthorityCreatorPermission within lemur/auth/permissions.py. When the configuration flags ADMIN ONLY AUTHORITY CREATION and LEMUR STRICT ROLE ENFORCEMENT are unset, they default to False, causing the flask principal.Permission. init () function to be called with no Need objects. Because the Permission.allows() function returns True when the needs set is empty, the .can() authorization gate permits any authenticated identity, including users with the read-only role.This allows a low-privilege user to perform administrative actions via the following API endpoints:
- 'POST /api/1/authorities'
- 'POST /api/1/certificates/upload'
- 'POST /api/1/pending certificates//upload'
- 'POST /api/1/notifications'
- 'PUT /api/1/notifications/'
- 'DELETE /api/1/notifications/'
- 'POST /api/1/domains'
Exploitation enables the creation of root Certificate Authorities, uploading of arbitrary certificates, creation of domain entries, and the creation or modification of notifications that reach an SSRF (Server-Side Request Forgery) sink—a vulnerability where an attacker can force the server to make requests to an unintended location.
Recommendations
Update Lemur to version 1.9.1 or later.
Ensure that the configuration flags
ADMIN ONLY AUTHORITY CREATION and LEMUR STRICT ROLE ENFORCEMENT are either left unset or explicitly set to True.Exploit
Fix
Incorrect Authorization
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Lemur