CVE-2024-28233VulnerabilityPublished 3 Apr 2024Updated 10 Sep 2026

CVE-2024-28233: JupyterHub · XSS

Affects jupyterhubSource GCVE Database

Not known to be exploited : upgrade to 4.1.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.1.0

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jupyterhub to 4.1.0.

Patches and advisories

github.com/jupyterhub/jupyterhub/commit/e2798a088f5ad45340fe79cdf1386198e664f77f (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamijupyterhub`pkg:bitnami/jupyterhub`Other threats	Affected <4.1.0	Fixed in 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade JupyterHub to version 4.1.0 or later, where this vulnerability is fixed. No additional mitigation is required once the patch is applied.

Description

A cross-site scripting (XSS) vulnerability exists in JupyterHub versions prior to 4.1.0. By tricking a user into visiting a malicious subdomain, an attacker can execute script code in the context of the user's session. This vulnerability affects single-origin JupyterHub deployments and those with user-controlled applications on subdomains. Exploitation could grant full access to the JupyterHub API and the user's single-user server. The issue is fixed in version 4.1.0.

References

Community reviews

Loading reviews…