CVE-2024-41942 | JupyterHub has a privilege escalation vulnerability with the `admin:users` scope

JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Prior to versions 4.1.6 and 5.1.0, if a user is granted the `admin:users` scope, they may escalate their own privileges by making themselves a full admin user. The impact is relatively small in that `admin:users` is already an extremely privileged scope only granted to trusted users. In effect, `admin:users` is equivalent to `admin=True`, which is not intended. Note that the change here only prevents escalation to the built-in JupyterHub admin role that has unrestricted permissions. It does not prevent users with e.g. `groups` permissions from granting themselves or other users permissions via group membership, which is intentional. Versions 4.1.6 and 5.1.0 fix this issue.

Published: 2024-08-08 Last update: 2024-08-12 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-41942 is rated Low Risk (38.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.10%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2024-41942

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 2025-11-21 0.25% 0.10% -0.15%
2 2025-11-18 0.10% 0.25% +0.16%
3 2025-09-16 0.10%

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-41942

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.
1.2 5.9 [email protected]
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.
1.2 5.9 [email protected]

Weakness enumeration for CVE-2024-41942

GitHub Security Advisory for CVE-2024-41942

GHSA-9x4q-3gxw-849f · Severity: high · Ecosystem: pip — JupyterHub has a privilege escalation vulnerability with the `admin:users` scope

OS Trackers for CVE-2024-41942

vendor priority summary link
debian not yet assigned CVE-2024-41942 not yet assigned priority: Debian including 1 source packages (jupyterhub), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 3, open 1. https://security-tracker.debian.org/tracker/CVE-2024-41942
ubuntu medium CVE-2024-41942 medium priority: Ubuntu including 1 source packages (jupyterhub), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 4, ignored 2, DNE 1. https://ubuntu.com/security/CVE-2024-41942

Affected software / configurations for CVE-2024-41942

Vendor Product Version Raw CPE
jupyter jupyterhub < 4.1.6 cpe:2.3:a:jupyter:jupyterhub:*:*:*:*:*:*:*:*
jupyter jupyterhub 5.0.0 cpe:2.3:a:jupyter:jupyterhub:5.0.0:-:*:*:*:*:*:*
jupyter jupyterhub 5.0.0 cpe:2.3:a:jupyter:jupyterhub:5.0.0:beta1:*:*:*:*:*:*
jupyter jupyterhub 5.0.0 cpe:2.3:a:jupyter:jupyterhub:5.0.0:beta2:*:*:*:*:*:*

References for CVE-2024-41942

cvelogic Threat Intelligence