https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 02:42:10 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-5855 EUVD-2026-5855 https://cve.radiocsirt.org/vuln/euvd-2026-5855 https://cve.radiocsirt.org/vuln/fkie_cve-2024-37300 <p>OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. This worked fine prior to JupyterHub 5.0, because `allow_all` did not take precedence over `identity_provider`. Since JupyterHub 5.0, `allow_all` does take precedence over `identity_provider`. On a hub with the same config, now all users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored. This is a documented change in JupyterHub 5.0, but is likely to catch many users by surprise. OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions. As a workaround, do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> <p>OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. This worked fine prior to JupyterHub 5.0, because `allow_all` did not take precedence over `identity_provider`. Since JupyterHub 5.0, `allow_all` does take precedence over `identity_provider`. On a hub with the same config, now all users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored. This is a documented change in JupyterHub 5.0, but is likely to catch many users by surprise. OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions. As a workaround, do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-37300 https://cve.radiocsirt.org/vuln/ghsa-gprj-3p75-f996 <p><strong>Affected:</strong> PyPI: oauthenticator</p> <p>### Impact</p> <p>JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:</p> <p>```python # Require users to be using the &#34;foo.horse&#34; identity provider, often an institution or university c.GlobusAuthenticator.identity_provider = &#34;foo.horse&#34; # Allow everyone who has that identity provider to log in c.GlobusAuthenticator.allow_all = True ```</p> <p>This worked fine prior to JupyterHub 5.0, because `allow_all` *did not* take precedence over `identity_provider`.</p> <p>Since JupyterHub 5.0, `allow_all` *does* take precedence over `identity_provider`. On a hub with the same config, now **all** users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored.</p> <p>This is a [documented change](https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users) in JupyterHub 5.0, but is likely to catch many users by surprise.</p> <p>### Patches</p> <p>OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.</p> <p>### Workarounds</p> <p>Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> <p><strong>Affected:</strong> PyPI: oauthenticator</p> <p>### Impact</p> <p>JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:</p> <p>```python # Require users to be using the &#34;foo.horse&#34; identity provider, often an institution or university c.GlobusAuthenticator.identity_provider = &#34;foo.horse&#34; # Allow everyone who has that identity provider to log in c.GlobusAuthenticator.allow_all = True ```</p> <p>This worked fine prior to JupyterHub 5.0, because `allow_all` *did not* take precedence over `identity_provider`.</p> <p>Since JupyterHub 5.0, `allow_all` *does* take precedence over `identity_provider`. On a hub with the same config, now **all** users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored.</p> <p>This is a [documented change](https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users) in JupyterHub 5.0, but is likely to catch many users by surprise.</p> <p>### Patches</p> <p>OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.</p> <p>### Workarounds</p> <p>Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> https://cve.radiocsirt.org/vuln/ghsa-gprj-3p75-f996 https://cve.radiocsirt.org/vuln/pysec-2026-1711 <p><strong>Affected:</strong> PyPI: oauthenticator</p> <p>### Impact</p> <p>JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:</p> <p>```python # Require users to be using the &#34;foo.horse&#34; identity provider, often an institution or university c.GlobusAuthenticator.identity_provider = &#34;foo.horse&#34; # Allow everyone who has that identity provider to log in c.GlobusAuthenticator.allow_all = True ```</p> <p>This worked fine prior to JupyterHub 5.0, because `allow_all` *did not* take precedence over `identity_provider`.</p> <p>Since JupyterHub 5.0, `allow_all` *does* take precedence over `identity_provider`. On a hub with the same config, now **all** users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored.</p> <p>This is a [documented change](https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users) in JupyterHub 5.0, but is likely to catch many users by surprise.</p> <p>### Patches</p> <p>OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.</p> <p>### Workarounds</p> <p>Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> <p><strong>Affected:</strong> PyPI: oauthenticator</p> <p>### Impact</p> <p>JupyterHub &lt; 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. The configuration for this would look like:</p> <p>```python # Require users to be using the &#34;foo.horse&#34; identity provider, often an institution or university c.GlobusAuthenticator.identity_provider = &#34;foo.horse&#34; # Allow everyone who has that identity provider to log in c.GlobusAuthenticator.allow_all = True ```</p> <p>This worked fine prior to JupyterHub 5.0, because `allow_all` *did not* take precedence over `identity_provider`.</p> <p>Since JupyterHub 5.0, `allow_all` *does* take precedence over `identity_provider`. On a hub with the same config, now **all** users will be allowed to login, regardless of `identity_provider`. `identity_provider` will basically be ignored.</p> <p>This is a [documented change](https://jupyterhub.readthedocs.io/en/stable/howto/upgrading-v5.html#authenticator-allow-all-and-allow-existing-users) in JupyterHub 5.0, but is likely to catch many users by surprise.</p> <p>### Patches</p> <p>OAuthenticator 16.3.1 fixes the issue with JupyterHub 5.0, and does not affect previous versions.</p> <p>### Workarounds</p> <p>Do not upgrade to JupyterHub 5.0 when using `GlobusOAuthenticator` in the prior configuration.</p> https://cve.radiocsirt.org/vuln/pysec-2026-1711