CVE-2018-7206

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.)

Published: 2018-02-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-7206 is rated Moderate Risk (62.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.80%). EPSS rose +1.11% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-7206

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.69% 1.80% +1.11%
2 2025-03-30 1.33% 0.69% -0.64%
3 2025-03-29 — 1.33% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-7206

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2018-7206

GitHub Security Advisory for CVE-2018-7206

GHSA-8x3m-m3x9-54fj · Severity: high · Ecosystem: pip — JupyterHub OAuthenticator elevation of privilege

Affected software / configurations for CVE-2018-7206

Vendor Product Version Raw CPE
jupyter oauthenticator 0.6.0 cpe:2.3:a:jupyter:oauthenticator:0.6.0:*:*:*:*:*:*:*
jupyter oauthenticator 0.6.1 cpe:2.3:a:jupyter:oauthenticator:0.6.1:*:*:*:*:*:*:*
jupyter oauthenticator 0.7.0 cpe:2.3:a:jupyter:oauthenticator:0.7.0:*:*:*:*:*:*:*
jupyter oauthenticator 0.7.1 cpe:2.3:a:jupyter:oauthenticator:0.7.1:*:*:*:*:*:*:*
jupyter oauthenticator 0.7.2 cpe:2.3:a:jupyter:oauthenticator:0.7.2:*:*:*:*:*:*:*

References for CVE-2018-7206

cvelogic Threat Intelligence