CVE-2026-58437 Repository Visibility Manipulation via Git Push Options

Repository Visibility Manipulation via Git Push Options...

CVE-2026-58437

CVE-2026-58437 affects Gitea: Git push options repo.private and repo.template can alter an existing repo’s visibility or template status when pushed by an admin/owner, bypassing standard audits and notifications. Affected code path in routers/private/hook_post_receive.go reads push options and, i...

GO-2026-6047 Gitea: Repository Visibility Manipulation via Git Push Options in gitea.dev

Gitea: Repository Visibility Manipulation via Git Push Options in gitea.dev...

Gitea: Repository Visibility Manipulation via Git Push Options

Repository Visibility Manipulation via Git Push Options | Field | Value | |-------|-------| | Affected File | routers/private/hookpostreceive.go | | Affected Function | HookPostReceive | | Affected Lines | 173–225 | | Prerequisite | Attacker must have owner-level or admin collaborator access to t...

Insufficient Logging

Overview Affected versions of this package are vulnerable to Insufficient Logging through the processing of undocumented git push options in the HookPostReceive function. An attacker can change the visibility or template status of a repository without triggering audit logs, webhooks, or...

Insufficient Logging

Overview Affected versions of this package are vulnerable to Insufficient Logging through the processing of undocumented git push options in the HookPostReceive function. An attacker can change the visibility or template status of a repository without triggering audit logs, webhooks, or...

PT-2026-63303

Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description Gitea contains an issue where the post-receive git hook handler incorrectly processes git push options on existing repositories. Users with owner or admin-collaborator access can use the...

CVE-2026-3854

CVE-2026-3854 describes an RCE vulnerability in GitHub Enterprise Server arising during git push option handling. An attacker with push access could abuse unsanitized user-supplied push option values that are incorporated into internal service headers; because the header format uses a delimiter t...