CVE-2026-118535

Gitea scoped workflow trust kept after repository transfer

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with access to their Actions secrets and job tokens. A transfer now removes the owner-level registrations of the repository, and registrations whose source repository no longer belongs to the registering owner are ignored.

Analysis

AI-generated

Technical impact

A repository in Gitea that had been registered as a source of scoped workflows maintained that registration even after being transferred to a new owner. The new owner could then modify the workflow definitions, and those workflows continued to run in the original owner’s repositories, giving the new owner access to the former owner’s Actions secrets and job tokens. This flaw effectively exposes sensitive secrets and allows the attacker to execute code in the account of the previous owner, representing a privilege escalation and secret disclosure vulnerability.

Affected Systems

The vulnerability affects Gitea servers that utilize scoped workflows and allow repository transfers. Any Gitea instance running a version prior to 28.4.0 that has enabled scoped workflows is potentially exposed. The fix was introduced in Gitea 28.4.0, which removes owner‑level registrations upon transfer and ignores registrations from sources that no longer belong to the registering owner.

Risk and Exploitability

Because the flaw is triggered by a repository transfer, an attacker must first transfer a repository that is registered for scoped workflows. Once the transfer occurs, the attacker can modify the workflow files in the new repository; those changes will propagate to the original owner’s repositories, running with the original secrets. The lack of an EPSS score and absence from the KEV catalog indicate no publicly known exploits yet, but the severity of the potential secret exposure and code execution makes the threat significant. The exploit is relatively straightforward for an attacker with access to the transfer mechanism, suggesting a moderate to high likelihood of abuse in environments permitting untrusted transfers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or newer, which removes retained scoped workflow registrations after repository transfer.
  • Check that repositories transferred after the upgrade are not listed as sources of scoped workflows for the prior owner.
  • If any orphaned registrations remain, delete them manually or through the Gitea administration interface.
  • Limit repository transfers to trusted users or require administrative approval to prevent unauthorized changes to scoped workflows.

Generated by OpenCVE AI on November 15, 2026 at 22:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with access to their Actions secrets and job tokens. A transfer now removes the owner-level registrations of the repository, and registrations whose source repository no longer belongs to the registering owner are ignored.
Title Gitea scoped workflow trust kept after repository transfer
Weaknesses CWE-863
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:13 PM
Reserved
Nov 15, 2026, 8:29 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM