# CVE-2026-73219: CVAT: Denial of service with regards to automatic annotation

> A user with write access can block automatic annotation for other tasks by submitting inconsistent task and job IDs in CVAT.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-7xhx-3q27-xvcx

## What is CVE-2026-73219?

CVE-2026-73219 is a medium-severity denial of service vulnerability in cvat-ai cvat, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CVAT is an open source interactive video and image annotation tool for computer vision. From 2.17.0 until 2.72.0, a user with write access to a CVAT job can submit a batch automatic annotation request to RequestViewSet.create with inconsistent task and job IDs, and because the task ID determines the single active request slot, block automatic annotation for another task whose ID is known. This issue is fixed in version 2.72.0.

Weakness: CWE-1288 (Improper Validation of Consistency within Input)

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


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

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

## Is CVE-2026-73219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73219 is a medium-severity denial of service vulnerability in cvat-ai cvat, published on 11 Aug 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-73219 in the wild and no public exploit code.

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

## Sources

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

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