https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T17:49:33.291033+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-32107 EUVD-2026-32107 2026-10-15T17:49:33.297312+00:00 EUVD-2026-32107 https://cve.radiocsirt.org/vuln/fkie_cve-2021-42343 fkie_cve-2021-42343 2026-10-15T17:49:33.297341+00:00

An issue was discovered in the Dask distributed package before 2021.10.0 for Python. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.

 https://cve.radiocsirt.org/vuln/ghsa-hwqr-f3v9-hwxr GHSA-hwqr-f3v9-hwxr — Workers for local Dask clusters mistakenly listened on public interfaces 2026-10-15T17:49:33.297372+00:00

Affected: PyPI: distributed

Versions of `distributed` earlier than `2021.10.0` had a potential security vulnerability relating to single-machine Dask clusters.

Clusters started with `dask.distributed.LocalCluster` or `dask.distributed.Client()` (which defaults to using `LocalCluster`) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on `localhost`. A Dask cluster created using this method AND running on a machine that has these ports exposed could be used by a sophisticated attacker to enable remote code execution. Users running on machines with standard firewalls in place, or using clusters created via cluster objects other than `LocalCluster` (e.g. `dask_kubernetes.KubeCluster`) should not be affected. This vulnerability is documented in CVE-2021-42343, and was fixed in version `2021.10.0` (PR #5427).

 https://cve.radiocsirt.org/vuln/gsd-2021-42343 gsd-2021-42343 2026-10-15T17:49:33.297401+00:00 gsd-2021-42343 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11766-1 openSUSE-SU-2024:11766-1 — python38-distributed-2022.1.0-1.1 on GA media 2026-10-15T17:49:33.297412+00:00

python38-distributed-2022.1.0-1.1 on GA media

 https://cve.radiocsirt.org/vuln/pysec-2021-387 PYSEC-2021-387 2026-10-15T17:49:33.297428+00:00

Affected: PyPI: dask

An issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-42343 UBUNTU-CVE-2021-42343 2026-10-15T17:49:33.297447+00:00

Affected: Ubuntu:18.04:LTS: dask.distributed, Ubuntu:20.04:LTS: dask.distributed

An issue was discovered in the Dask distributed package before 2021.10.0 for Python. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.