Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 01 Nov 2026 10:00:00 +0000
| 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 |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-11-01T09:48:38.763Z
Reserved: 2026-11-01T08:50:49.248Z
Link: CVE-2026-116474
No data.
Status : Deferred
Published: 2026-11-01T10:18:35.170
Modified: 2026-11-01T10:18:35.283
Link: CVE-2026-116474
No data.
OpenCVE Enrichment
Updated: 2026-11-01T11:30:06Z
-
CWE-347
Improper Verification of Cryptographic Signature