# CVE-2026-75109: Determined Missing Authorization Check on Generic Task Endpoints

> Authenticated attackers can disrupt other users' workloads by terminating, pausing, or unpausing tasks they do not own due to missing authorization checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **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:** 17 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-62vf-9v93-9rf4

## What is CVE-2026-75109?

CVE-2026-75109 is a high-severity missing authorization vulnerability in determined-ai determined, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Determined fails to authorize requests on the generic task kill, pause, and unpause endpoints in the API handlers. Authenticated attackers can disrupt other users' workloads by terminating, pausing, or unpausing tasks they do not own.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75109 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75109 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75109 is a high-severity missing authorization vulnerability in determined-ai determined, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75109 exists.

Affected product: determined-ai determined. 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-75109/ (Markdown: https://insights.sbomify.com/CVE-2026-75109/index.md)
```

## Sources

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

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