AI Science Tracker

Gitea Actions job tokens can make user commits appear signed by the instance

Gitea self-hosted Git service · AI involvement attributed to Anthropic OSS Scanner (model unspecified)

Finding and attribution

A regular user who can run an Actions job can use its token to register an email and GPG key on the gitea-actions system account. Commit verification then presents that user’s commit as instance-signed and trusted, including in other users’ repositories. The advisory says the effect is on the displayed signer/trust level; it does not create signature validity or grant access, and signing-rule enforcement is unaffected.

Product: Gitea self-hosted Git service. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and Gitea maintainers.

CVE identifiers: CVE-2026-116474.

AI and human contribution (source account): The Gitea maintainer advisory directly says the finding was reported by the Anthropic OSS scanner, identifier ANT-2026-VMTM4XVM. It does not identify a model.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The maintainer published GHSA-mf6p-vqpw-3r7x on 2026-11-01 and lists CVE-2026-116474. The advisory demonstrates the behavior on a stock binary and marks severity moderate. It explicitly limits impact to displayed signer/trust status; this record makes no exploitation-in-the-wild claim.

Remediation status: fix documented. The advisory lists Gitea 28.3.0 as patched. Its recommended remediation combines rejecting account-data writes from non-positive job-token IDs with verifier logic that skips keys whose owner does not exist. It notes that previously planted database rows may need cleanup.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 1 Nov 2026. AI attribution dated 1 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 6.5. Documented technical effects: other.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-116474: other.
Prerequisites / affected scope: A user able to run a Gitea Actions workflow can make commits display as trusted and instance-signed. The source limits impact to displayed signature status; enforcement and access are unaffected..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: The advisory lists Gitea 28.3.0 as patched. Its recommended remediation combines rejecting account-data writes from non-positive job-token IDs with verifier logic that skips keys whose owner does not exist. It notes that previously planted database rows may need cleanup.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases