CoreCVE
Back

HIGH

jupyter-server authentication cookies remain valid after password reset due to static cookie secret

Published May 5, 2026

Description

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.

Affected products

Remediation

Red Hat statement

This Moderate flaw in Jupyter Server allows an attacker to retain authenticated access even after a password reset. In Red Hat deployments utilizing password-based authentication, a compromised session cookie remains valid because the signing secret is not rotated, undermining expected credential revocation. This impacts shared or public-facing servers where session invalidation is critical.

Weaknesses (1)

CWE-613

References (8)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner GitHub_M
Published May 5, 2026
Updated May 7, 2026
Reserved Apr 15, 2026
Link CVE-2026-40934

CISA Vulnrichment

Updated May 7, 2026

NVD

Status Analyzed
Modified Jul 25, 2026
Link CVE-2026-40934

Red Hat

Severity Moderate
Public date May 5, 2026
Bugzilla 2466909
Link CVE-2026-40934

ENISA EUVD

Assigner GitHub_M
Published May 5, 2026
Updated May 7, 2026
Link EUVD-2026-27513

GitHub

Link GHSA-5MRQ-X3X5-8V8F