Read the docs
TI-2026-83606 Aliases CVE-2026-119441

Gitea public-only token bypass in bulk organization repo deletion

Priority LOW 38CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-863.

Summary

Gitea from 1.27.0 before 28.3.0 does not enforce the public-only restriction of access tokens on the DELETE /api/v1/orgs/{org}/repos endpoint, which deletes all repositories of an organization. A public-only token of an owner of a public organization can permanently delete that organization's private repositories. The flaw is an incorrect authorization check (CWE-863).

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

`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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00256 17th percentileScored 2026-11-07
Fix Fixed Gitea (Gitea): 28.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GiteaGitea1.27.0 to before 28.3.028.3.0Patch availableCNA
  • Gitea VendorGitea Affected 1.27.0 to before 28.3.0 Fixed in 28.3.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*——Gitea
  • cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* Versions — — ·Gitea

Remediation

Upgrade Gitea to 28.3.0, which rejects public-only tokens on routes that require organization ownership.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA Gitea (Gitea) Fixed in 28.3.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Gitea 28.3.0

    20 records Highest priority Priority MEDIUM 3 MEDIUM, 17 LOW

    Other records, highest priority first

    • TI-2026-83610 Gitea OAuth2 auto-linking lets attackers take over accountsPriority MEDIUM 49
    • TI-2026-83601 Gitea public-only token can expose private OCI blobs through package mountsPriority MEDIUM 47
    • TI-2026-83594 Gitea public-only token bypass exposes private repository jobsPriority MEDIUM 47

Timeline

  1. 2026-11-01 Threatist record created from CVE-2026-119441
  2. 2026-11-06 CVSS score added · CISA ADP
  3. 2026-11-06 CISA SSVC decision points changed

References

  • TI-2026-42785 Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation. KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
  • TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
  • TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
  • TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
  • TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
See all 240 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences