CVE-2026-116474
No CVSS score yet. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
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.
- EPSS
- 0.1% estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-01. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-347 Improper Verification of Cryptographic Signature
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
ChatGPTClaudePerplexityGoogle AI Mode
Show the prompt
Explain CVE-2026-116474 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116474?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116474?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an estimate of exploitation activity across the internet over the next 30 days, not a prediction for my systems). Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.