Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-fvcq-4x64-hqxr

Jupyter Server Proxy allows users to run arbitrary external processes alongside their notebook server and provide authenticated web access to them. Versions of 3.x prior to 3.2.4 and 4.x prior to 4...

CVSS 9.7 CriticalCriticalEPSS 0.0044 · 38th percentile

Critical, because:

  • CVSS score 9.7: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 11 Jun 2024, 22:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
jupyter-server-proxyPyPI<7abc9dc5bbb0b4b440548a5375261b8b8192fc22 || >=3.0.0, <3.2.4 || >=4.1.2, <4.2.07abc9dc5bbb0b4b440548a5375261b8b8192fc22, 3.2.4, 4.2.0
Identifiers
GHSA-fvcq-4x64-hqxr · CVE-2024-35225 · PYSEC-2024-236
Weakness (CWE)
CWE-79 · CWE-116
Tags
Published
11 Jun 2024
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jupyter Server Proxy versions 3.0.0 to before 3.2.4 and 4.1.2 to before 4.2.0 are vulnerable to reflected cross-site scripting. An attacker who sends a user a crafted phishing link can run arbitrary JavaScript in the user's browser when they click it, gaining extensive access to their JupyterLab instance. Upgrade to version 3.2.4 or 4.2.0; if that is not possible, disable the jupyter-server-proxy extension.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.7 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 38th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 11 Jun 2024. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.