Jupyter JupyterHub 5.0.0
Approved changes feed: RSS · Atom
cpe:2.3:a:jupyter:jupyterhub:5.0.0:-:*:*:*:*:*:*
part: a version: 5.0.0 update: -
| Vendor | Jupyter (3170fc95-7dab-5fb9-942d-251eb444755d) |
|---|---|
| Product | Jupyterhub (17080f79-8994-5355-9bfb-a3cb333041b2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/jupyterhub/jupyterhub |
purl2cpe | 2026-06-01 10:17:17.475818 |
pkg:github/jupyterhub/jupyterhub |
purl2cpe | 2026-06-01 10:17:17.475820 |
pkg:pypi/jupyterhub |
purl2cpe | 2026-06-01 10:17:17.475821 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-41942 |
vulnerable | 2026-06-03 14:56:35.468202 |
JupyterHub has a privilege escalation vulnerability with the `admin:users` scope
HIGH (7.2)
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-08T14:36:44.498Z
Updated: 2024-08-08T15:17:06.179Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.