CVE-2026-40934
Jupyter Server is the backend for Jupyter web applications. In …
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the secret used to sign authentication cookies is persisted to a static file at ~/.local/share/jupyter/runtime/jupyter_cookie_secret and is never rotated when a user changes their password. After a password reset and server restart, any previously issued authentication cookie remains cryptographically valid because the signing key has not changed. An attacker who has captured a session cookie through any means retains full authenticated access to the server regardless of subsequent password changes. This affects deployments using password-based authentication, particularly shared or public-facing servers where credential rotation is expected to revoke existing sessions. This issue has been fixed in version 2.18.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/jupyter-server/jupyter_server/security/advisories/GHSA-5mrq-x3x5-8v8f
- github.com/advisories/GHSA-5mrq-x3x5-8v8f
- nvd.nist.gov/vuln/detail/CVE-2026-40934
- github.com/pypa/advisory-database/tree/main/vulns/jupyter-server/PYSEC-2026-69.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-40934
- cve.org/CVERecord?id=CVE-2026-40934
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.