# CVE-2026-119441: Gitea public-only token bypass on bulk organization repository deletion


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-jh8p-x4ch-389q

## What is CVE-2026-119441?

CVE-2026-119441 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. 

### Official description

`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-119441 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119441 is a high-severity vulnerability in Gitea, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119441 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-119441/ (Markdown: https://insights.sbomify.com/CVE-2026-119441/index.md)
```

## Sources

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

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