# CVE-2026-97204: Gitea label deletion across repository and organization IDs

> A user with write access to a repository can delete organization labels due to ID collision, allowing unauthorized data modification.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A: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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-fxq4-gr55-7x5g

## What is CVE-2026-97204?

CVE-2026-97204 is a low-severity missing authorization vulnerability in Gitea, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Deleting a label compared the ID of the repository in the request against the organization ID of organization labels, and the two ID sequences overlap. A user with write access to the issues of a repository could therefore delete the labels of an organization that has the same numeric ID as that repository. Labels are now deleted only within their own repository or organization.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-97204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97204 is a low-severity missing authorization vulnerability in Gitea, published on 18 Oct 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-97204 in the wild and no public exploit code.

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

## Sources

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

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