Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Gitea 28.4.0 Fixes Four Distinct Security Paths

Gitea 28.4.0 security fixes address service-account execution, Actions secrets, TOTP guessing, and hash exposure. Check conditions and upgrade.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
16 November 2026
Reading time
6 min read
Abstract Gitea instance and four distinct security review paths.

Gitea 28.4.0 security fixes change the upgrade decision for teams that stopped at 28.3.0. Gitea released 28.4.0 on 15 November 2026 and urges users to update promptly. The release fixes a repository initialization path that could run commands as the Gitea service account, alongside separate Actions, TOTP, and password-hash exposure flaws.

The earlier Gitea 28.3.0 upgrade analysis remains useful for its earlier fixes. It is no longer the final version decision for these newly disclosed issues. Check the deployed build and relevant features, use a vulnerability intelligence platform to organize the review, then schedule 28.4.0 with a rollback plan and post-change verification.

Gitea 28.4.0 Security Fixes: Four Different Exposure Paths

These issues do not share one entry point. The repository flaw needs an authenticated user who may create and push to repositories. The Actions issue depends on an owner-level scoped workflow source that is transferred. The TOTP issue needs a known password, while the search disclosure needs a signed-in user and a visible repository with a commit status.

Issue Condition to check Potential result 28.4.0 change
CVE-2026-125423 User can create and push to an automatically initialized repository using the Default README; timing and server layout also matter. Commands may run as the Gitea service account. Initialization uses a fresh directory and blocks pushes until ready.
CVE-2026-118535 A registered source of owner-scoped Actions workflows is transferred to a new owner. The new owner may change workflows that still access the previous owner’s secrets and tokens. Transfer removes the registration.
CVE-2026-123002 Someone already knows the password of an account protected by TOTP. Repeated code guesses may defeat the second factor. Five failed codes trigger a 15-minute account refusal.
CVE-2026-123006 A signed-in user can see a repository with a commit status. The repository owner’s password hash, salt, and email may be returned. The response is limited to status state and target URL.

Gitea describes all four fixes in its 28.4.0 release announcement. Its advisory for CVE-2026-125423 lists 28.3.0 and earlier as affected and 28.4.0 as patched. The TOTP advisory gives the same version boundary for CVE-2026-123002. For the other two, use the release’s 28.4.0 fix statement and verify the installed build rather than assuming a separate branch has the patch.

Why Can Repository Creation Reach the Service Account?

Gitea says this path requires a signed-in user permitted to create and push to a repository that uses automatic initialization with the Default README. A timing window and a compatible server-side layout must also align. If the path succeeds, commands run with the Gitea service account’s privileges.

The Gitea advisory calls this an authenticated, timing-dependent path. It says the tested setup also needed a compatible server-side filesystem layout. The advisory does not claim unauthenticated access, root privileges, or a container escape. Its laboratory confirmation is evidence of a working test, not evidence of an incident on a production server.

For triage, prioritize instances where non-administrative users can create repositories. The patch changes both sides of the race: it builds initial content in a fresh directory and waits before accepting pushes. If an upgrade must wait, a temporary restriction on repository creation can reduce one prerequisite. That restriction is our interim risk decision, not a substitute for the vendor patch.

Which Teams Have Actions, TOTP, or Search Exposure?

CVE-2026-118535 concerns a source repository registered for owner-level scoped workflows. Gitea says that registration persisted after transfer, allowing the new owner to modify workflows that ran in the former owner’s repositories. Those runs retained access to Actions secrets and job tokens. Review transferred workflow-source repositories and the registrations they previously served before judging which owners need a secrets review.

CVE-2026-123002 is different: the attacker must already know the account password. Gitea says wrong TOTP codes were not limited during sign-in, password reset, or Basic authentication with the one-time-code header. Its fix rejects further attempts for 15 minutes after five failures. The TOTP advisory details the missing control; password compromise and second-factor guessing are separate facts to investigate.

CVE-2026-123006 concerns data returned by repository search, not password plaintext. Gitea says the response included a repository owner’s full user record from version 28.0.0 when the repository had a commit status.

A signed-in user who could see that repository could receive its owner’s hash, salt, and email address. The fix reduces the returned fields. Assess visible repositories with commit statuses and account exposure without assuming hashes were taken or cracked.

The three distinctions matter for the upgrade queue. Restricting repository creation would not repair a retained workflow registration, TOTP guessing, or the search response. Similarly, MFA does not compensate for a response that discloses password hashes. Teams should prioritize the 28.4.0 release, then examine each relevant feature and account path separately.

What Evidence Should Drive the Upgrade and Follow-up?

First, record the exact running version for every Gitea instance, including staging and internally reachable installations. Compare it with the 28.4.0 release, and note whether users can create repositories or use Actions. Inventory transfers of registered workflow sources and identify owners whose workflows inherited those sources. This gives the team a concrete review scope after patching.

28.4.0 change and review order
  • Inventory instancesRecord version, owner, and repository-creation permissions.
  • Upgrade with a rollback planApply the vendor 28.4.0 build using the normal change process.
  • Verify the running buildConfirm each instance reports 28.4.0 after restart.
  • Review scoped workflowsCheck transferred sources, registrations, and affected secrets.
  • Review account and search exposureExamine suspicious sign-ins and access to visible repositories with commit statuses.

For CVE-2026-125423, preserve repository-creation and Git-service logs around suspicious initialization activity if those records exist. For the Actions issue, compare transfer history with workflow executions and access to secrets. For TOTP, review authentication activity across the flows Gitea names. For the search issue, use available access records and affected-account inventories; the release note alone cannot show who received a response.

The review should not assume that a Gitea-specific check exists. If investigation identifies possible compromise, follow the organization’s incident response plan template for evidence preservation and credential review. Confirm the running build and configuration after the change window closes.

How Much Does Current Discussion Change the Decision?

Brandefense Blackhole counted two dark-chat posts mentioning CVE-2026-125423, three mentioning CVE-2026-118535, and two mentioning CVE-2026-123002 between 18 August and 16 November 2026. The measured unit is posts mentioning each identifier. These counts may overlap, so they must not be added as a unique-discussion total. A mention does not establish exploitation or an affected organization.

The dated CISA KEV snapshot in the source pack, catalog version 2026.11.13, did not list these four CVEs. That is a catalog observation, not a prediction of future status. The immediate reason to upgrade is Gitea’s published fix and the conditions described above. Teams should keep the four investigation tracks distinct while moving all applicable instances to 28.4.0.

Frequently Asked Questions

Does Gitea 28.3.0 contain these four fixes?

Gitea's 28.4.0 release describes these fixes. Its repository-initialization and TOTP advisories list 28.3.0 and earlier as affected, with 28.4.0 patched.

Does the repository issue require administrator access?

No. Gitea's advisory describes a signed-in user permitted to create and push to a repository. Exploitation also depends on timing and a compatible server layout.

Does discussion of the CVEs prove active exploitation?

No. Brandefense Blackhole counts posts mentioning identifiers, not incidents. Investigate local evidence while applying the vendor update.

Sources

  1. Gitea: 28.4.0 release announcement
  2. Gitea: repository auto-initialization advisory
  3. Gitea: TOTP rate-limit advisory
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →