https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 09:56:28 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1138 certfr-2025-avi-1138 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1138 https://cve.radiocsirt.org/vuln/fkie_cve-2025-34351 <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor&#39;s product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).</p> <p>Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor&#39;s product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022).</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-34351 https://cve.radiocsirt.org/vuln/ghsa-gx77-xgc2-4888 <p><strong>Affected:</strong> PyPI: ray</p> <p>Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.</p> <p><strong>Affected:</strong> PyPI: ray</p> <p>Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.</p> https://cve.radiocsirt.org/vuln/ghsa-gx77-xgc2-4888 https://cve.radiocsirt.org/vuln/pysec-2026-518 <p><strong>Affected:</strong> PyPI: ray</p> <p>Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.</p> <p><strong>Affected:</strong> PyPI: ray</p> <p>Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access.</p> https://cve.radiocsirt.org/vuln/pysec-2026-518