Read the docs

Gitea lets read-only users push to repositories being created

Priority LOW 23CWE-862Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
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-862.

Summary

Gitea from 1.16.0 before 28.4.0 lets a user with read access push branches and tags to a repository that is still being created by a migration, fork or template generation. The server-side hooks that enforce write access are not yet in place during that window, which is missing authorization (CWE-862). An authenticated remote user with read access can write to the repository, and the same can happen after a failed migration leaves it in that state.

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

Description from the CNA

Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00149 4th percentileScored 2026-11-16
Fix Fixed Gitea (Gitea): 28.4.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
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.16.0 to before 28.4.028.4.0Patch availableCNA
  • Gitea VendorGitea Affected 1.16.0 to before 28.4.0 Fixed in 28.4.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 version 28.4.0, which refuses Git over HTTP requests to repositories that are still being created. Fixed in Gitea 28.4.0 only; no vendor advisory identifier is listed in the sources.

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

  • Fix · CNA Gitea (Gitea) Fixed in 28.4.0

Fixed in the same release

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

  • Release ·

    Gitea 28.4.0

    19 records Highest priority Priority LOW 19 LOW

    Other records, highest priority first

    • TI-2026-91976 Command execution in Gitea through repository auto-initializationPriority LOW 39
    • TI-2026-91985 Protected file pattern bypass in Gitea with quoted file namesPriority LOW 36
    • TI-2026-91982 Gitea missing attempt limit for TOTP passcodesPriority LOW 34

Timeline

  1. 2026-11-15 Threatist record created from CVE-2026-129337
  2. 2026-11-16 CVSS score added · CISA ADP
  3. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-42785 Remote code execution in Gitea diffpatch API through Git hooks 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 260 →

Sources

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