# CVE-2026-10705: dask HLL hyperloglog.py nunique_approx resource consumption

> Remote attackers can cause resource exhaustion in dask via the nunique_approx function, leading to denial of service.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10705, GHSA-qp9q-4rh4-m8jc, UBUNTU-CVE-2026-10705

## What is CVE-2026-10705?

CVE-2026-10705 is a low-severity denial of service vulnerability in dask, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in dask up to 3.0. Affected by this issue is the function nunique_approx of the file dask/dataframe/hyperloglog.py of the component HLL Handler. This manipulation causes resource consumption. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The pull request to fix this issue awaits acceptance.

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-10705?


## How do I fix CVE-2026-10705?

No fix has been published for CVE-2026-10705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10705 being exploited?

There is no known exploitation of CVE-2026-10705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10705 and fix it if it is affected.

What it is: CVE-2026-10705 is a low-severity denial of service vulnerability in dask, published on 3 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10705 in the wild and no public exploit code.

Affected product: dask. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10705/ (Markdown: https://insights.sbomify.com/CVE-2026-10705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10705
- OSV: https://osv.dev/vulnerability/CVE-2026-10705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10705/
Summaries are generated and may contain mistakes; the official description above is the record.