CVE-2026-119441 json
Gitea public-only token bypass on bulk organization repository deletion
published 2026-11-01 8 d ago modified 2026-11-06 2 d ago also EUVD-2026-114805
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
`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.
Patch / fix
- Gitea Gitea 28.3.0
- github.com/go-gitea/gitea#39690 pull request
- github.com/go-gitea/gitea#39853 pull request
- github.com/go-gitea/gitea/releases/tag/v28.3.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/go-gitea/gitea/pull/39690
patch
-
github.com
/go-gitea/gitea/pull/39853
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-jh8p-x4ch-389q
vendor-advisory
-
blog.gitea.com
/release-of-28.3.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.3.0
release-notes
Sources
- CVE List CVE-2026-119441
- NVD CVE-2026-119441
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.