CVE-2026-116474

Gitea Actions job token spoofing of instance-signed commits

Published Nov 1, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as activated. Commit verification treats a key without a real owner as the instance signing key, so any user who can run a workflow job could make commits signed with their own key show as trusted and signed by the instance in every repository where they appear, including pull requests to repositories the user cannot write to. The impact is limited to the displayed signature status: enforcement such as required signed commits only checks that a signature is verified and is unaffected, and no access is gained. The `/api/v1/user` routes now reject system users.

Analysis

AI-generated

Technical impact

The vulnerability allows a Gitea Actions job to authenticate as the gitea-actions system user, enabling the job to register an email address and a GPG key on that user without email confirmation. Because the key is not linked to a real owner, commit verification treats it as the instance signing key. Consequently, any user who can run a workflow job can make commits signed with their own key appear to be legitimately instance‑signed in all repositories where the key is present, including pull requests to repositories to which the user has no write permission. The impact is limited to the displayed signature status; enforcement mechanisms that require signed commits check only that a signature is valid, so no actual access or control over repository content is obtained.

Affected Systems

The affected vendor is Gitea, product Gitea. Any Gitea instance running a version prior to the 28.3.0 release is susceptible to the token‑spoofing flaw. The published fix is included in the 28.3.0 release and later versions.

Risk and Exploitability

The vulnerability does not provide a path to denial of service or arbitrary code execution, and the exploit probability is indicated by an EPSS score of < 1%. It is not listed in the CISA KEV catalog. The primary attack vector, which is inferred from the description, requires an attacker to be able to execute a Gitea Actions workflow job, which typically means possessing push or workflow‑execution permissions on a repository. Because the flaw only affects signature verification, the risk level is moderate, but the lack of confirmed exploitation data means it is unlikely to be widely targeted. The CVSS score is 6.5, providing a moderate severity assessment.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.3.0 or later to apply the patch that rejects system users on the /api/v1/user endpoints.
  • Disable or restrict the ability for users to run Gitea Actions workflow jobs, or enforce email confirmation for GPG key registration, to prevent unauthorized key association.
  • Audit existing GPG keys associated with the gitea-actions system user and revoke any that were added without proper confirmation.

Generated by OpenCVE AI on November 6, 2026 at 18:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as activated. Commit verification treats a key without a real owner as the instance signing key, so any user who can run a workflow job could make commits signed with their own key show as trusted and signed by the instance in every repository where they appear, including pull requests to repositories the user cannot write to. The impact is limited to the displayed signature status: enforcement such as required signed commits only checks that a signature is verified and is unaffected, and no access is gained. The `/api/v1/user` routes now reject system users.
Title Gitea Actions job token spoofing of instance-signed commits
Weaknesses CWE-347
References
Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 6, 2026, 3:33 PM
Reserved
Nov 1, 2026, 8:50 AM
Status
Deferred
Published
Nov 1, 2026, 10:18 AM
Modified
Nov 6, 2026, 4:17 PM