{"answers":{"affected":"3 open source packages ship an affected version, including distributed. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23528 in the wild and no public exploit code.","fix":"Upgrade distributed to 2026.1.0 or later.","what":"CVE-2026-23528 is a medium-severity cross-site scripting vulnerability in dask distributed, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-23528 and fix it if it is affected.\n\nWhat it is: CVE-2026-23528 is a medium-severity cross-site scripting vulnerability in dask distributed, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-23528 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- distributed (PyPI): affected all versions; fixed in 2026.1.0\n- distributed (PyPI): affected all versions; fixed in 2026.1.0\n- distributed (PyPI): affected all versions; fixed in 2026.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-23528/ (Markdown: https://insights.sbomify.com/CVE-2026-23528/index.md)","id":"CVE-2026-23528","markdown":"https://insights.sbomify.com/CVE-2026-23528/index.md","name":"CVE-2026-23528","record":{"aliases":["DEBIAN-CVE-2026-23528","GHSA-c336-7962-wfj2","PYSEC-2026-169","UBUNTU-CVE-2026-23528"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Dask distributed library","requires_auth":"none","summary":"Attackers can execute arbitrary code via XSS in the Dask dashboard when used with Jupyter, requiring user interaction with a malicious link.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dask","vendor":"anaconda"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"Dask distributed is a distributed task scheduler for Dask. Prior to 2026.1.0, when Jupyter Lab, jupyter-server-proxy, and Dask distributed are all run together, it is possible to craft a URL which will result in code being executed by Jupyter due to a cross-side-scripting (XSS) bug in the Dask dashboard. It is possible for attackers to craft a phishing URL that assumes Jupyter Lab and Dask may be running on localhost and using default ports. If a user clicks on the malicious link it will open an error page in the Dask Dashboard via the Jupyter Lab proxy which will cause code to be executed by the default Jupyter Python kernel. This vulnerability is fixed in 2026.1.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Dask distributed Vulnerable to Remote Code Execution via Jupyter Proxy and Dashboard","id":"CVE-2026-23528","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Arbitrary File Read in Google BigQuery Sink connector","id":"CVE-2026-23529"},"packages":[{"ecosystem":"PyPI","fixed":["2026.1.0"],"introduced":["0"],"last_affected":[],"package":"distributed","purl":null,"source":"GHSA-c336-7962-wfj2"},{"ecosystem":"PyPI","fixed":["2026.1.0"],"introduced":["0"],"last_affected":[],"package":"distributed","purl":"pkg:pypi/distributed","source":"GHSA-c336-7962-wfj2"},{"ecosystem":"PyPI","fixed":["2026.1.0"],"introduced":["0"],"last_affected":[],"package":"distributed","purl":"pkg:pypi/distributed","source":"PYSEC-2026-169"}],"prev":{"headline":"h3 v1 has Request Smuggling (TE.TE) issue","id":"CVE-2026-23527"},"products":["distributed"],"published":"2026-01-16","related":[{"cvss_score":9.8,"headline":"Workers for local Dask clusters mistakenly listened on public interfaces","id":"CVE-2021-42343","kev_date_added":null,"published":"2021-10-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-16","vendors":["dask"]},"summary":"Attackers can execute arbitrary code via XSS in the Dask dashboard when used with Jupyter, requiring user interaction with a malicious link.","url":"https://insights.sbomify.com/CVE-2026-23528/"}