TI-2026-68544 Aliases CVE-2026-79960

Deploy key pushes act as repository owner in Gitea

LOW 31CWE-863Published 2026-10-06 · Updated 2026-10-07

Key facts

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

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

Summary

Gitea through 1.27.3 records the repository owner as the pusher when a push is authenticated with a deploy key, so permission checks evaluate the owner instead of the key. An attacker holding a writable deploy key can create protected tags without being on the tag allow list and change repository visibility through push options. Pull requests created through the AGit flow with a deploy key are also attributed to the owner. The flaw is an incorrect authorization issue (CWE-863).

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.00212 11th percentileScored 2026-11-07

Fix No fix listed No fixed version in the sources yet

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

Vendor	Product	Affected versions	Fixed in	Status	Source
Gitea	Gitea	up to 1.27.3	—	No fix listed	CNA

Gitea VendorGitea Affected up to 1.27.3 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPE	Versions	Role	Vendor
cpe:2.3:a:gitea:gitea::::::::	before 28.0.0	Vulnerable	Gitea

cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* Versions before 28.0.0 Vulnerable ·Gitea

Remediation

The sources list no fixed version for Gitea.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

2026-10-06 Threatist record created from CVE-2026-79960
2026-10-07 CVSS score added · CISA ADP
2026-10-07 CISA SSVC decision points changed

References

Patch 1

Fix: go-gitea/gitea pull request #37306

Advisory 1

GitHub Security Advisory GHSA-7769-9pr9-m24h

Other 2

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-2020-11072 The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote… CVSS 3.1HIGH 7.2
TI-2022-12910 Gitea before 1.16.7 does not escape git fetch remote. CVSS 3.1HIGH 7.5
TI-2019-08404 models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror… CVSS 3.1HIGH 8.8
TI-2022-00955 Open Redirect on login in go-gitea/gitea CVSS 3.1MEDIUM 6.1
TI-2026-68968 Push-to-create bypass of FORCE_PRIVATE policy in Gitea CVSS 3.1MEDIUM 5.4

See all 80 →

Sources

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