Bug 2564526 (CVE-2026-116474)
| Summary: | CVE-2026-116474 code.gitea.io/gitea: Gitea: Commit signature spoofing via system user key registration | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability-draft | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | gbenhaim, niyer, twaugh |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Gitea. The automated workflow system permits jobs to register an email address and a GNU Privacy Guard (GPG) cryptographic key to an internal system account via user API endpoints. Because commit verification treats keys associated with system accounts as official instance keys, an authenticated user capable of running workflow jobs can forge trusted instance signatures on arbitrary commits. This allows untrusted commits across repositories to falsely display as verified and signed by the instance, misleading users about commit authenticity.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
OSIDB Bzimport
2026-11-01 09:51:29 UTC
|