Skip to main content
VulnerabilityPublished

CVE-2026-116474: Gitea · Improper Verification of Cryptographic Signature

Affects GiteaSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 28.3.0 when convenient.

Data as of 1 Nov 2026, 10:07 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 28.3.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade Gitea and go-gitea/gitea to 28.3.0.

Affected software

ProductAffectedFixed in
Giteagitea.devAffected
  • >=1.19.0 <28.3.0
Fixed in
  • 28.3.0
GitHubgo-gitea/giteapkg:github/go-gitea/giteaOther threatsAffected
  • >=1.19.0 <28.3.0
Fixed in
  • 28.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Gitea to version 28.3.0 or later, where the API endpoints reject system users such as 'gitea-actions', preventing unauthorized registration of emails and GPG keys. No additional action is required as the fix fully addresses the issue.

Description

A vulnerability in Gitea Actions allows a workflow job authenticated as the system user 'gitea-actions' to register an email address and GPG key without email confirmation, causing commits signed with that key to appear as trusted and signed by the instance. This affects signature display status but does not grant access or bypass enforcement of signed commits. The issue is fixed in version 28.3.0.

References

Community reviews

Loading reviews…