CVE-2026-96589 Gitea private repository access retained after rejected transfer

When a private repository is transferred to a user who lacks access, Gitea grants that recipient temporary read access as a collaborator so they can review the repository. Rejecting or cancelling the transfer did not revoke this collaboration, so the named recipient kept persistent read access to...

CVE-2026-96589

The Gitea platform contains a vulnerability where a user who lacks access to a private repository is granted temporary read access as a collaborator during a repository transfer process. If the owner rejects or cancels the transfer, the system fails to revoke this collaboration, resulting in the ...

CVE-2026-79960 Gitea deploy key pushes acting as the repository owner

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

CVE-2026-79960

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

CVE-2026-79960 Gitea deploy key pushes acting as the repository owner

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

CVE-2026-79960

The Gitea repository management platform contains a vulnerability where pushes authenticated with a deploy key are incorrectly recorded as being performed by the repository owner. This Incorrect Authorization (CWE-863) causes permission checks in the push hook pipeline to evaluate the owner's pri...

CVE-2026-79960 Gitea deploy key pushes acting as the repository owner

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

CVE-2026-70357

The Gitea repository migration functionality is vulnerable to a Server-Side Request Forgery (SSRF) via DNS rebinding . While Gitea validates the migration hostname against network allow and block lists, the Git subprocess independently resolves the hostname during the Git clone operation . An att...

CVE-2026-70357 Gitea repository migration SSRF through DNS rebinding

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between...

CVE-2026-70357

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between...

CVE-2026-70357 Gitea repository migration SSRF through DNS rebinding

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between...

CVE-2026-70357 Gitea repository migration SSRF through DNS rebinding

Gitea validates a repository migration hostname against its network allow and block lists before invoking Git, but the Git subprocess independently resolves the hostname when connecting. An attacker who can start a migration and control the destination's DNS can change the address between...

CVE-2026-104636

Gitea is vulnerable to a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) because the application validates the initial remote URL for push mirrors, wiki remote checks, and migrated pull request fetches, but fails to revalidate the destination during subsequent raw Git operations follow...

CVE-2026-104636 Gitea SSRF through Git HTTP redirects in mirrors and fetches

Gitea validated the initial remote URL for push mirrors, wiki remote checks, and fetches of migrated pull request heads, but the subsequent raw Git operations followed HTTP redirects without revalidating the destination. A repository administrator using a policy-allowed endpoint that redirects...

EUVD-2026-93909

Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns multiple DNS answers, because the address that was validated was not necessarily the address Git later connected to. A low-privileged user who can create migrations or mirrors could direct th...

CVE-2026-101029

The Gitea repository migration and pull mirror features are vulnerable to a Server-Side Request Forgery (SSRF) due to a Time-of-check Time-of-use (TOCTOU) race condition. The egress checks can be bypassed by using a hostname that returns multiple DNS answers , as the address validated by the syst...

EUVD-2026-93908

When migrations ALLOWEDDOMAINS was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it resolve to loopback or...

CVE-2026-101027 Gitea migration SSRF through ALLOWED_DOMAINS address check bypass

When migrations ALLOWEDDOMAINS was configured, a hostname matching the allow list was accepted without checking its resolved address against the local-network restrictions. A user who can start repository migrations and control the DNS of an allowed hostname could make it resolve to loopback or...

CVE-2026-96890 Server-Side Request Forgery vulnerability was identified in GitHub Enterprise Server that allowed requests to attacker-controlled internal hosts

A Server-Side Request Forgery SSRF vulnerability was identified in GitHub Enterprise Server that allowed a repository contributor to cause the appliance to issue requests to attacker-controlled internal hosts, which could be chained to achieve remote code execution on the appliance. The secret...

CVE-2026-103620

A missing authorization vulnerability in GitHub Enterprise Server allows repository collaborators with write access to delete the current default branch using the GraphQL API . This flaw enables an attacker to set an attacker-controlled branch as the new default. In repositories requiring pull-re...