Lemur manages TLS certificate creation. Prior to 1.9.1, StrictRolePermission and AuthorityCreatorPermission in lemur/auth/permissions.py call flask_principal.Permission.__init__() with zero Need objects when ADMIN_ONLY_AUTHORITY_CREATION and LEMUR_STRICT_ROLE_ENFORCEMENT are unset because both flags default to False. Flask-Principal Permission.allows() returns True when self.needs is empty, so the .can() authorization gate permits every authenticated identity, including the read-only role. A read-only user can access POST /api/1/authorities, POST /api/1/certificates/upload, POST /api/1/pending_certificates//upload, POST /api/1/notifications, PUT or DELETE /api/1/notifications/, and POST /api/1/domains to create root Certificate Authorities, upload arbitrary certificates, create or edit notifications that reach an SSRF sink, and create domain entries. Explicitly setting either flag to False continues to opt into the permissive behavior. This issue is fixed in version 1.9.1.
CVE-2026-48508
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
August 18, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026Authorization bypass in StrictRolePermission / AuthorityCreatorPermission · Advisory · Netflix/lemur · GitHub
https://github.com/Netflix/lemur/security/advisories/GHSA-qcqw-jwxc-2hqgv1.9.1
Patch available: Netflix/lemur v1.9.1
https://github.com/Netflix/lemur/releases/tag/v1.9.1commit e6a41e2c1b20 (Netflix/lemur)
Patch available: Netflix/lemur v1.9.1 (contains commit e6a41e2c1b20)
https://github.com/Netflix/lemur/commit/e6a41e2c1b2028840d19039b06895524a19ad36fVendor Advisories for CVE-2026-48508(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| lemur | 0.11.0 ... 1.9.0 (18 versions) | 1.9.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 13× 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.
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 01:20 UTCEG score recompute
- 2026-08-24 13:09 UTCEG score recompute
- 2026-08-22 10:12 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 07:24 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 07:02 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 19:45 UTCEG score recompute
- 2026-08-18 18:25 UTCEG score recompute
- 2026-07-30 14:02 UTCEG score recompute
- 2026-07-26 14:56 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-25 19:46 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-48508?
When was CVE-2026-48508 disclosed?
Is CVE-2026-48508 actively exploited?
What is the CVSS score of CVE-2026-48508?
How do I remediate CVE-2026-48508?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48508
Is Your Infrastructure Affected by CVE-2026-48508?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.