{
  "id": "gitea-november-28-4",
  "url": "https://ohshit.app/incidents/gitea-november-28-4/",
  "title": "Gitea 28.4.0 fixes command execution and repository owner password hash exposure",
  "level": 3,
  "level_name": "sharted",
  "date": "2026-11-15",
  "date_is_approximate": false,
  "updated": null,
  "tags": [
    "Gitea",
    "RCE",
    "Credentials",
    "Actions"
  ],
  "ecosystems": [],
  "summary": "Gitea 28.4.0 fixes a repository creation race that can lead to command execution as the service account, and a dashboard search that exposed repository owners’ password hash material to signed-in users.",
  "splash": "Self-hosted Gitea up to 28.3.0. The command execution path needs an account that can create and push to a repository and win a race.",
  "wipe": "Upgrade to Gitea 28.4.0 or later. Review repository creation and Actions logs, and reset potentially exposed owner passwords.",
  "in_the_wild": "unknown",
  "source_exception": null,
  "cves": [
    {
      "id": "CVE-2026-125423",
      "name": "Repository creation race",
      "description": "Users allowed to create and push to repositories can race auto-initialization and overwrite a server hook via a symlink."
    },
    {
      "id": "CVE-2026-123006",
      "name": "Repository owner credential exposure",
      "description": "A signed-in user can obtain password hash material and email addresses of owners of visible repositories with a commit status."
    },
    {
      "id": "CVE-2026-123065",
      "name": "Cross-release attachment deletion",
      "description": "Someone with release write access can delete another attachment's stored file if they know its UUID."
    },
    {
      "id": "CVE-2026-123638",
      "name": "Protected file pattern bypass",
      "description": "A writer can bypass protected file patterns because Gitea matched names against Git's quoted output."
    },
    {
      "id": "CVE-2026-126338",
      "name": "Cross-repository review context leak",
      "description": "A signed-in user with a review ID can copy diff context from a repository they cannot read."
    },
    {
      "id": "CVE-2026-120729",
      "name": "Issue hover stored XSS",
      "description": "A crafted issue reference to attacker-controlled content can run script when another user hovers over it."
    },
    {
      "id": "CVE-2026-118535",
      "name": "Workflow trust survives repository transfer",
      "description": "After a repository registered as an owner-scoped workflow source is transferred, the new owner can modify workflows that still run with the former owner's repository secrets and token."
    },
    {
      "id": "CVE-2026-123002",
      "name": "Unlimited TOTP attempts",
      "description": "An attacker who already knows an account password can repeatedly guess its six-digit TOTP."
    },
    {
      "id": "CVE-2026-123009",
      "name": "Fork retains upstream code access",
      "description": "A user with an existing fork can copy a base branch through the web editor after losing upstream read permission."
    },
    {
      "id": "CVE-2026-118389",
      "name": "RubyGems compact index injection",
      "description": "A registry publisher can use newlines in gem metadata to inject index entries. This fix first shipped in 28.3.0."
    },
    {
      "id": "CVE-2026-129525",
      "name": "Issue and pull request permission confusion",
      "description": "Shared routes could expose issue or pull request data to users with only the other permission. Earlier releases covered some API routes."
    },
    {
      "id": "CVE-2026-128365",
      "name": "Actions approval satisfies required review",
      "description": "In the organization that owns team ID 2, a user who can change review requests can make an Actions approval count toward required approvals."
    },
    {
      "id": "CVE-2026-129337",
      "name": "Write access during repository provisioning",
      "description": "A user with read access can push over HTTP before a migration, fork or template-created repository has its hooks."
    },
    {
      "id": "CVE-2026-129341",
      "name": "Former uploader can remove a release asset",
      "description": "A previous uploader with sufficient read access can delete the asset after losing write rights."
    },
    {
      "id": "CVE-2026-120991",
      "name": "Shared package blob removal",
      "description": "On instances enforcing a package quota, a rejected upload can delete blobs shared with other packages when the uploader has matching bytes."
    },
    {
      "id": "CVE-2026-123642",
      "name": "AGit bypasses pull request permissions",
      "description": "A user or deploy key with code read access or wiki write access can open a pull request through AGit without pull request access."
    },
    {
      "id": "CVE-2026-125617",
      "name": "Hidden organization role disclosure",
      "description": "A signed-in user can look up another user's role in a public or limited organization."
    },
    {
      "id": "CVE-2026-128359",
      "name": "Disabled user can obtain OAuth2 tokens",
      "description": "When Gitea is an OAuth2 or OIDC provider, an existing refresh token or unused authorization code can yield new tokens after account deactivation."
    },
    {
      "id": "CVE-2026-120725",
      "name": "Anonymous Git LFS reads",
      "description": "Git LFS ignores required sign-in for non-private repositories if the requester knows the repository path and object SHA-256."
    },
    {
      "id": "CVE-2026-127958",
      "name": "Draft review disclosure",
      "description": "Draft reviews created through the API can appear in timelines and notifications before submission."
    }
  ],
  "fixed": [
    {
      "product": "Gitea",
      "version": "28.4.0"
    }
  ],
  "checklist": [
    {
      "title": "Upgrade the Gitea instance",
      "hint": "Back up the database, configuration and repositories. Follow Gitea’s upgrade procedure for your deployment, restart the service and verify the running version with gitea --version inside the service environment."
    },
    {
      "title": "Review possible exposure through repository search",
      "hint": "On installations that ran 28.0.0 through 28.3.0, check proxy logs for unusual GET /repo/search use if logs are available. Identify owners of visible repositories with a commit status and reset passwords that may have been exposed. Ask owners to change reused passwords on other services."
    },
    {
      "title": "Investigate suspect hooks and workflows",
      "hint": "Correlate new auto-initialized repository pushes with changes to post-receive.d/gitea and unexpected processes under the service account. Review owner-scoped workflow sources that changed hands and rotate affected secrets if unauthorized runs occurred. A hook change alone does not prove compromise."
    }
  ],
  "sources": [
    {
      "name": "Gitea 28.4.0 release announcement",
      "url": "https://blog.gitea.com/release-of-28.4.0/",
      "says": "Lists the release batch and earlier partial fixes.",
      "primary": true
    },
    {
      "name": "Gitea repository initialization advisory",
      "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946",
      "says": "Documents tested versions, exploit conditions and the 28.4.0 patch.",
      "primary": true
    },
    {
      "name": "Gitea repository search advisory",
      "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-frjx-8pcw-8c9q",
      "says": "Documents vulnerable versions and exposed password material.",
      "primary": true
    },
    {
      "name": "Gitea workflow transfer advisory",
      "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-q3q9-39vr-q35j",
      "says": "Shows when a transferred source can access secrets in consuming workflows.",
      "primary": true
    }
  ],
  "headline": null,
  "one_liner": null,
  "in_the_wild_note": "The maintainer published lab reproduction details. Live exploitation is unconfirmed.",
  "mitigation": null,
  "timeline": [
    {
      "date": "Nov 15, 2026",
      "title": "Gitea publishes 28.4.0 and its security advisories",
      "body": "The maintenance release closes the initialization race, restricts repository search output and repairs other access control and workflow issues."
    }
  ],
  "body_markdown": "The initialization race, CVE-2026-125423, needs repository creation and push rights, automatic initialization with the default README, and a server layout where a crafted symlink can resolve to a writable Git hook. Successful execution has the operating system permissions of the Gitea service. The advisory documents reproduction on 28.3.0, 28.2.0, 1.27.1 and 1.25.5. Turning off user-defined Git hooks alone does not close this path.\n\nThe repository search leak, CVE-2026-123006, affects 28.0.0 through 28.3.0. Access requires a signed-in account and a visible repository with a commit status. The advisory demonstrates the exposure through public repositories with a commit status. The material includes hashes, salts, and primary email addresses and can support offline password guessing. The source does not establish which accounts, if any, were targeted.\n\nThe [official upgrade documentation](https://docs.gitea.com/installation/upgrade-from-gitea) covers deployment-specific steps. If you suspect service account command execution, preserve evidence, isolate the affected instance, and rotate exposed credentials from a trusted system before restoring service.\n\nThe 28.4.0 binaries also use Go 1.27.4 for the HTTP server fix already covered in the [Go November advisory](/incidents/go-november-security/). Some Gitea fixes shipped earlier. The RubyGems index fix first shipped in 28.3.0, and parts of the issue and pull request authorization fix shipped in 28.2.0 and 28.3.0. Upgrade to the full release to pick up the remaining fixes."
}