How severe is CVE-2022-21697?

CVE-2022-21697 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-21697?

CVE-2022-21697 affects the following packages: jupyter-server-proxy (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-21697?

Update jupyter-server-proxy to 3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21697 is resolved across your whole dependency graph.

How do I detect CVE-2022-21697 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyter-server-proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-21697 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2022-21697 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-21697 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-21697?

CVE-2022-21697 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-21697?

CVE-2022-21697 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-21697 published, and has it been updated?

CVE-2022-21697 was published on January 25, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2022-21697 — jupyter-server-proxy

MEDIUMFix: jupyterhub/jupyter-server-proxy@fd31930

CVE-2022-21697 is a medium-severity (CVSS 6.3) Server-Side Request Forgery (SSRF) vulnerability in jupyter-server-proxy. A fix is available for jupyter-server-proxy — see the affected versions and patch details below.

SSRF vulnerability (requires authentication)

Also known asGHSA-gcv9-6737-pjqwPYSEC-2022-16

Published

Jan 25, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-21697.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍jupyter-server-proxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Server-Side Request Forgery ( SSRF )

Who is impacted? Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.

A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the allowed_hosts check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.

Patches

Has the problem been patched? What versions should users upgrade to?

Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch

For more information

If you have any questions or comments about this advisory:

Open a topic on our forum
Email the Jupyter security team at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`jupyter-server-proxy`	all versions	3.2.1`pip install --upgrade 'jupyter-server-proxy==3.2.1'`

Affected Products

1 product · 1 configurations

Application

jupyter server proxyjupyter

< 3.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyter-server-proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jupyter-server-proxy to 3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21697 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### Impact **What kind of vulnerability is it?** Server-Side Request Forgery ( SSRF ) **Who is impacted?** Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled. A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Upgrade

O3 Security · Impact-Aware SCA

Is CVE-2022-21697 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

jupyter-server-proxy

5.3/10

Maintained10/10

Code-Review5/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Jan 25, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-21697

GHSA-gcv9-6737-pjqw

PYSEC-2022-16

References

Advisorygithub.com · CVE 2022 21697.json Advisorygithub.com · GHSA gcv9 6737 pjqw Advisorynvd.nist.gov · CVE 2022 21697 Fixgithub.com · fd31930bacd12188c448c886e0783529436b99eb Webgithub.com · v3.2.0...v3.2.1.patch Webgithub.com · jupyter server proxy Webgithub.com · PYSEC 2022 16.yaml

Related vulnerabilities

Also affects jupyter-server-proxy

This CVE is medium severity; 2 of 2 other CVEs affecting jupyter-server-proxy are rated as high or higher (top: critical).

CVE-2024-35225CVE-2024-28179

Same weakness: CWE-918

This CVE is medium severity; 6 of 6 other CVEs with CWE-918 are rated as high or higher (top: high).

CVE-2026-28385GHSA-7wpf-ch8f-5f4xCVE-2026-54442GHSA-4mfg-r38w-w8fgCVE-2026-118660CVE-2026-108360Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026