# CVE-2026-73221: CVAT: Flawed authorization logic in endpoints related to lambda requests


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-m7p7-6w4m-886p

## What is CVE-2026-73221?

CVE-2026-73221 is a medium-severity vulnerability in cvat-ai cvat, published on 11 Aug 2026. 

### 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 the Worker role can use predictable task-based request IDs with the lambda request retrieve and destroy endpoints to view automatic annotation requests for tasks or jobs the user cannot access and cancel requests initiated by other users. This issue is fixed in version 2.72.0.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-73221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73221 is a medium-severity vulnerability in cvat-ai cvat, published on 11 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-73221 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-73221/ (Markdown: https://insights.sbomify.com/CVE-2026-73221/index.md)
```

## Sources

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

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