Bug 2564526 (CVE-2026-116474) - CVE-2026-116474 code.gitea.io/gitea: Gitea: Commit signature spoofing via system user key registration
Summary: CVE-2026-116474 code.gitea.io/gitea: Gitea: Commit signature spoofing via sys...
Keywords:
Status: NEW
Alias: CVE-2026-116474
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-01 09:51 UTC by OSIDB Bzimport
Modified: 2026-11-03 08:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-01 09:51:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.