# CVE-2026-76073: Label Studio through 1.23.0 Cross-Organization Annotation Access via Unscoped AnnotationAPI Queryset

> Authenticated users can access, modify, or delete annotations from other organizations due to missing object-level authorization checks in the API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:** Yes
- **Published:** 24 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-f3mm-hmc7-j4qg, MINI-9386-984x-c7x7

## What is CVE-2026-76073?

CVE-2026-76073 is a high-severity missing authorization vulnerability in HumanSignal label-studio, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Label Studio does not scope the annotation detail endpoint to the requesting user's organization. AnnotationAPI in label_studio/tasks/api.py declares queryset = Annotation.objects.all() and provides no get_queryset override, so the default lookup retrieves any annotation by primary key. The view's permission_required entries name annotations.view, annotations.change and annotations.delete, and label_studio/core/permissions.py registers every permission with rules.is_authenticated, so the check is satisfied by any logged-in account and no object-level organization test runs. The sibling task endpoint does constrain its queryset with project__organization set to the requester's active organization, which is the boundary this path omits. Annotation identifiers are sequential integers, so an authenticated user of one organization can enumerate identifiers to read, modify and delete annotations belonging to other organizations on the same instance. The same unscoped queryset appears on AnnotationConvertAPI in the same file.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

Apply the vendor's patch.

## Is CVE-2026-76073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76073 is a high-severity missing authorization vulnerability in HumanSignal label-studio, published on 24 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-76073 in the wild and no public exploit code.

Affected product: HumanSignal label-studio. 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-76073/ (Markdown: https://insights.sbomify.com/CVE-2026-76073/index.md)
```

## Sources

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

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