Gitea 28.4.0 Fixes Repository Command Execution and Account Data Exposure

P1 — VALIDATE AND UPDATEHigh · 8.8 (CVSS v3.1, CVE-2026-123006); other advisory scores varyEXPLOITATION: NOT STATED

Quick Answer

Upgrade affected Gitea servers to 28.4.0. Check repository creation, owner data exposure, workflow trust and package registries; validate access controls and retain deployment evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Gitea versions, deployment images, repository-creation permissions, Actions trust sources, package registries, Git LFS settings and service owners. Match each deployed version to the linked project advisory. Repository auto-init abuse requires the ability to create repositories; password-hash disclosure requires a signed-in user and a visible repository with commit status. Deploy the official 28.4.0 release using the established upgrade procedure. Include every application instance and container image; preserve a consistent backup of the database, repositories, configuration and package storage before maintenance. Confirm running versions, test repository creation and Git operations, and verify that repository search omits owner password material. Test scoped workflow transfers, disabled-user OAuth token issuance, TOTP attempt limits, LFS access and package downloads.

Open the authoritative advisory

Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeGitea server, Actions integrations and package registries
AdvisoryGitea 28.4.0 / GHSA-frjx-8pcw-8c9q / GHSA-6m4f-m9vc-7946 / GHSA-49c9-hm8q-6rvq / GHSA-q3q9-39vr-q35j / GHSA-8pmc-9g44-v9gw / GHSA-wmr3-xg9x-vc55 / GHSA-q8pg-ggp9-rm9m / GHSA-5mx6-8rwm-52wf / GHSA-9vh6-6hgj-j5m5 / GHSA-4p89-xcq8-xfhm / GHSA-w87g-xmrp-86v2 / GHSA-9827-6wh6-634q / GHSA-7mr2-v9gc-4467 / GHSA-wgx7-537g-xfrg / GHSA-859w-9wv7-c5x9 / GHSA-jrjr-q3rq-f899 / GHSA-74jf-6hjp-549c / GHSA-8cjj-9p56-j54f / GHSA-jr33-w6w7-86vj / GHSA-qrrc-h266-v49p
CVEsCVE-2026-118389, CVE-2026-118535, CVE-2026-120725, CVE-2026-120729, CVE-2026-120991, CVE-2026-123002, CVE-2026-123006, CVE-2026-123009, CVE-2026-123065, CVE-2026-123638, CVE-2026-123642, CVE-2026-125423, CVE-2026-125617, CVE-2026-126338, CVE-2026-127958, CVE-2026-128359, CVE-2026-128365, CVE-2026-129337, CVE-2026-129341, CVE-2026-129525, CVE-2026-97054
Authoritative release date2026-11-15 19:39:47 UTC — official Gitea 28.4.0 release; the 20 project advisories were published at 21:03 UTC on the same day.
Authority revision dateNo separate material advisory revision is confirmed.
Affected versionsAffected ranges differ by advisory, as listed below. The password-hash disclosure affects 28.0.0 through 28.3.0; repository auto-initialization command execution affects versions through 28.3.0. RubyGems compact-index injection affects versions through 28.2.0.
Fixed versionGitea 28.4.0; RubyGems compact-index injection was already fixed in 28.3.0
CVSS base score8.8 (CVSS v3.1, CVE-2026-123006); other advisory scores vary
CVSS severityHigh
Exploitation statusThe cited Gitea release and project advisories do not confirm exploitation in the wild; no exploitation claim is inferred.

What Changed

Gitea released 28.4.0 and disclosed 20 application vulnerabilities. The release closes repository initialization, account-data, access-control, workflow-trust and package-storage flaws. Its binaries also include Go 1.27.4 for CVE-2026-97054. The RubyGems flaw is newly disclosed here but was fixed in 28.3.0.

Advisory-Specific Version Boundaries

The 8.8 overview score belongs to CVE-2026-123006; it is not a release-wide rating. Preserve each project advisory's range and score when assessing individual deployments.

<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-frjx-8pcw-8c9q">CVE-2026-123006</a>Affected: >= 28.0.0, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 8.8 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946">CVE-2026-125423</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 8.5 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-49c9-hm8q-6rvq">CVE-2026-118389</a>Affected: <= 28.2.0. Fixed: 28.3.0. Official severity: High; CVSS base score: 8.1 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-q3q9-39vr-q35j">CVE-2026-118535</a>Affected: >= 1.27.0, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 7.3 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-8pmc-9g44-v9gw">CVE-2026-120725</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: Low; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-wmr3-xg9x-vc55">CVE-2026-120729</a>Affected: >= 1.27, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-q8pg-ggp9-rm9m">CVE-2026-120991</a>Affected: >= 1.20, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-5mx6-8rwm-52wf">CVE-2026-123002</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 8.2 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-9vh6-6hgj-j5m5">CVE-2026-123009</a>Affected: >= 1.25, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 7.7 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-4p89-xcq8-xfhm">CVE-2026-123065</a>Affected: >= 1.15, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 8.5 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-w87g-xmrp-86v2">CVE-2026-123638</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: 8.5 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-9827-6wh6-634q">CVE-2026-123642</a>Affected: >= 1.16, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-7mr2-v9gc-4467">CVE-2026-125617</a>Affected: >= 1.16, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-wgx7-537g-xfrg">CVE-2026-126338</a>Affected: >= 1.14.0, <= 28.3.0. Fixed: 28.4.0. Official severity: High; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-859w-9wv7-c5x9">CVE-2026-127958</a>Affected: >= 1.12, <= 28.3.0. Fixed: 28.4.0. Official severity: Low; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-jrjr-q3rq-f899">CVE-2026-128359</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: 5.4 (see advisory for CVSS version).
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-74jf-6hjp-549c">CVE-2026-128365</a>Affected: >= 1.19, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f">CVE-2026-129337</a>Affected: >= 1.16, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-jr33-w6w7-86vj">CVE-2026-129341</a>Affected: >= 1.11, <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: Not provided by the authority.
<a href="https://github.com/go-gitea/gitea/security/advisories/GHSA-qrrc-h266-v49p">CVE-2026-129525</a>Affected: <= 28.3.0. Fixed: 28.4.0. Official severity: Moderate; CVSS base score: 4.3 (see advisory for CVSS version).

What To Validate Now

  1. Inventory. Record Gitea versions, deployment images, repository-creation permissions, Actions trust sources, package registries, Git LFS settings and service owners.
  2. Establish applicability. Match each deployed version to the linked project advisory. Repository auto-init abuse requires the ability to create repositories; password-hash disclosure requires a signed-in user and a visible repository with commit status.
  3. Remediate. Deploy the official 28.4.0 release using the established upgrade procedure. Include every application instance and container image; preserve a consistent backup of the database, repositories, configuration and package storage before maintenance.
  4. Validate. Confirm running versions, test repository creation and Git operations, and verify that repository search omits owner password material. Test scoped workflow transfers, disabled-user OAuth token issuance, TOTP attempt limits, LFS access and package downloads.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Treat server patching and historical exposure assessment separately. Preserve relevant repository-search, account, Actions and package logs; investigate possible credential or secret exposure when the affected configuration and activity justify it. Test integrations that depend on newly restricted API responses. Avoid restoring old application binaries against a changed database without a compatible recovery plan.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.