PatchSiren cyber security CVE debrief
CVE-2026-119441 Gitea CVE debrief
CVE-2026-119441 is a vulnerability in the Gitea platform that allows for the deletion of all repositories of an organization using a public-only access token. The vulnerability exists because the DELETE /api/v1/orgs/{org}/repos route only checks if the organization is public, but does not enforce the public-only restriction of access tokens. This means that a public-only token of an owner of a public organization could be used to permanently delete the organization's private repositories.
- Vendor
- Gitea
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-11-01
- Original CVE updated
- 2026-11-01
- Advisory published
- 2026-11-01
- Advisory updated
- 2026-11-01
Who should care
Defenders who use Gitea should verify the affected versions and apply the necessary patches to prevent exploitation. Gitea administrators should restrict access to the DELETE /api/v1/orgs/{org}/repos route to only allow authorized users.
Why it matters
CVE-2026-119441 is a vulnerability in Gitea that allows for the deletion of all repositories of an organization using a public-only access token. Defenders should prioritize verifying the affected versions and applying patches.
- An attacker could delete all repositories of an organization using a public-only access token
- Defenders need to verify the affected versions of Gitea and apply the necessary patches
- Defenders should restrict access to the DELETE /api/v1/orgs/{org}/repos route to only allow authorized users
Technical summary
The DELETE /api/v1/orgs/{org}/repos route in Gitea does not enforce the public-only restriction of access tokens, allowing a public-only token of an owner of a public organization to permanently delete the organization's private repositories. This vulnerability exists because the route only checks if the organization is public, but does not verify the access token's scope. Defenders should prioritize verifying the affected versions of Gitea and applying the necessary patches to prevent exploitation. The vulnerability can be mitigated by restricting access to the DELETE /api/v1/orgs/{org}/repos route to only allow authorized users.
Defensive priority
Defenders should prioritize verifying the affected versions of Gitea and applying the necessary patches to prevent exploitation.
Recommended defensive actions
- Verify the affected versions of Gitea and apply the necessary patches
- Restrict access to the DELETE /api/v1/orgs/{org}/repos route to only allow authorized users
- Monitor for suspicious activity on the Gitea platform
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability was reported by an unknown source and is described in the CVE record and the Gitea security advisory. The affected versions of Gitea need to be verified by defenders. The CVE record was published on 2026-11-01T10:18:36.643Z and has not been modified since then. Evidence is limited to public sources and CVE details. Defenders should verify the Gitea security advisory for specific version information and apply necessary patches.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-119441 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-119441
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-119441 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-119441
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://blog.gitea.com/release-of-28.3.0/
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39690
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39853
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/releases/tag/v28.3.0
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/security/advisories/GHSA-jh8p-x4ch-389q
88ee5874-cf24-4952-aea0-31affedb7ff2
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.