https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 17:05:32 +0000 https://cve.radiocsirt.org/vuln/cve-2024-28188 <p><strong>Affected:</strong> jupyter-server jupyter-scheduler, jupyter scheduler</p> <p>Jupyter Scheduler is collection of extensions for programming jobs to run now or run on a schedule. The list of conda environments of `jupyter-scheduler` users maybe be exposed, potentially revealing information about projects that a specific user may be working on. This vulnerability has been patched in version(s) 1.1.6, 1.2.1, 1.8.2 and 2.5.2.</p> <p><strong>Affected:</strong> jupyter-server jupyter-scheduler, jupyter scheduler</p> <p>Jupyter Scheduler is collection of extensions for programming jobs to run now or run on a schedule. The list of conda environments of `jupyter-scheduler` users maybe be exposed, potentially revealing information about projects that a specific user may be working on. This vulnerability has been patched in version(s) 1.1.6, 1.2.1, 1.8.2 and 2.5.2.</p> https://cve.radiocsirt.org/vuln/cve-2024-28188 https://cve.radiocsirt.org/vuln/ghsa-v9g2-g7j4-4jxc <p><strong>Affected:</strong> PyPI: jupyter-scheduler</p> <p>### Impact</p> <p>`jupyter_scheduler` is missing an authentication check in Jupyter Server on an API endpoint (`GET /scheduler/runtime_environments`) which lists the names of the Conda environments on the server. In affected versions, `jupyter_scheduler` allows an unauthenticated user to obtain the list of Conda environment names on the server. This reveals any information that may be present in a Conda environment name.</p> <p>This issue does **not** allow an unauthenticated third party to read, modify, or enter the Conda environments present on the server where `jupyter_scheduler` is running. This issue only reveals the list of Conda environment names.</p> <p>Impacted versions: `&gt;=1.0.0,&lt;=1.1.5 ; ==1.2.0 ; &gt;=1.3.0,&lt;=1.8.1 ; &gt;=2.0.0,&lt;=2.5.1`</p> <p>### Patches</p> <p>* `jupyter-scheduler==1.1.6` * `jupyter-scheduler==1.2.1` * `jupyter-scheduler==1.8.2` * `jupyter-scheduler==2.5.2`</p> <p>### Workarounds</p> <p>Server operators who are unable to upgrade can disable the `jupyter-scheduler` extension with:</p> <p>``` jupyter server extension disable jupyter-scheduler ```</p> <p>### References</p> <p>If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting</p> <p><strong>Affected:</strong> PyPI: jupyter-scheduler</p> <p>### Impact</p> <p>`jupyter_scheduler` is missing an authentication check in Jupyter Server on an API endpoint (`GET /scheduler/runtime_environments`) which lists the names of the Conda environments on the server. In affected versions, `jupyter_scheduler` allows an unauthenticated user to obtain the list of Conda environment names on the server. This reveals any information that may be present in a Conda environment name.</p> <p>This issue does **not** allow an unauthenticated third party to read, modify, or enter the Conda environments present on the server where `jupyter_scheduler` is running. This issue only reveals the list of Conda environment names.</p> <p>Impacted versions: `&gt;=1.0.0,&lt;=1.1.5 ; ==1.2.0 ; &gt;=1.3.0,&lt;=1.8.1 ; &gt;=2.0.0,&lt;=2.5.1`</p> <p>### Patches</p> <p>* `jupyter-scheduler==1.1.6` * `jupyter-scheduler==1.2.1` * `jupyter-scheduler==1.8.2` * `jupyter-scheduler==2.5.2`</p> <p>### Workarounds</p> <p>Server operators who are unable to upgrade can disable the `jupyter-scheduler` extension with:</p> <p>``` jupyter server extension disable jupyter-scheduler ```</p> <p>### References</p> <p>If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting</p> https://cve.radiocsirt.org/vuln/ghsa-v9g2-g7j4-4jxc