-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-44405
•
published on May 5, 2026
In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
-
CVE-2026-40934
•
published on May 5, 2026
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.
