CVE-2026-119441None▾ Sunlit`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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.1%
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.
gitea.dev >= 1.27.0 < 28.3.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-117685NoneGitea public-only package token access to private OCI blobs
CVE-2026-118394NoneGitea OAuth2 userinfo private group disclosure to public-only tokens
CVE-2026-116289NoneGitea public-only token bypass through Actions runner registration
CVE-2026-119627NoneGitea limited-visibility profile disclosure with public-only tokens
CVE-2026-119625NoneGitea user and organization feed token scope bypass
CVE-2026-118395NoneGitea public-only token bypass in repository and organization creation