Summary
generated automatically from NVD dataProject Jupyter JupyterHub OAuthenticator versions 0.6.0 to 0.6.1 and 0.7.0 to 0.7.2 contain an access control flaw in GitLab group whitelisting. Group membership was not checked correctly, so GitLab users outside the whitelisted groups could create their own accounts on the Hub linked to their GitLab account. They could not access other users' accounts, and GitLab authentication without gitlab_group_whitelist and other Authenticators are unaffected. The CVSS v3.1 score is 8.8 (HIGH).
NVD description
An issue was discovered in Project Jupyter JupyterHub OAuthenticator 0.6.x before 0.6.2 and 0.7.x before 0.7.3. When using JupyterHub with GitLab group whitelisting for access control, group membership was not checked correctly, allowing members not in the whitelisted groups to create accounts on the Hub. (Users were not allowed to access other users' accounts, but could create their own accounts on the Hub linked to their GitLab account. GitLab authentication not using gitlab_group_whitelist is unaffected. No other Authenticators are affected.)
EPSS · FIRST.org
1.8%probability of exploitation in the next 30 days
Higher than 78% of scored CVEs
EPSS (Exploit Prediction Scoring System) estimates, from observed exploitation activity, how likely a CVE is to be exploited in the next 30 days. It complements CVSS, which measures severity, not likelihood. Score of 2026-10-29, recomputed daily by FIRST.org.
CVSS v3.1 Score
Information
- Published
- 18 févr. 2018
- Updated
- 17 juin 2026
- Status
- Modified
- Source
- cve@mitre.org
Affected products
Bounds published by NVD: "< 8.4.27" means 8.4.27 is no longer vulnerable. The fixed release to install is in the vendor advisory.
Weaknesses (CWE)
References (6)
- https://github.com/jupyterhub/oauthenticator/blob/8499dc2/CHANGELOG.md#073---2018-02-16Release NotesVendor Advisory
- https://github.com/jupyterhub/oauthenticator/blob/8499dc2/CHANGELOG.md#073---2018-02-16Release NotesVendor Advisory
Similar CVEs
Other vulnerabilities of type
Know which CVEs hit the versions you run.
Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.