CVE-2026-104627 Gitea CVE debrief

Who should care

Defenders responsible for Gitea instances, especially those with OpenID login enabled, should assess exposure and apply patches or mitigations as needed to prevent attackers from attaching their identity to a victim's account and signing in as the victim. This includes verifying the exposure of Gitea instances, reviewing compensating controls, and monitoring for potential exploitation attempts.

Why it matters

Defenders should prioritize verifying exposure of Gitea instances, especially those with OpenID login enabled, and apply patches or mitigations as needed to prevent attackers from attaching their identity to a victim's account and signing in as the victim.

• attackers could attach their identity to a victim's account
• attackers could sign in as the victim through OpenID login

Technical summary

The Gitea OpenID association callback accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. This allows an attacker-controlled OpenID provider to attach the attacker's identity to the account of a signed-in victim who has opened a crafted link. The attacker can then sign in as the victim through OpenID login, which does not apply the local TOTP or WebAuthn checks. The fix requires a time-limited 'state' value bound to the user, enhancing session binding security.

Defensive priority

Defenders should prioritize verifying exposure of Gitea instances, especially those with OpenID login enabled, and apply patches or mitigations as needed.

Recommended defensive actions

• Verify Gitea instance exposure, especially with OpenID login enabled
• Apply patches or mitigations as needed
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, its impact, and the fix. However, additional information on affected versions and potential exploitation is limited. The CVE Program record (cve-org) and NIST NVD detail page (nvd) offer official perspectives on the vulnerability. Vendor advisory information is available through source references (ref-4, ref-5).

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.