CVE-2026-104627None▾ SunlitThe Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-contr…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-controlled OpenID provider could attach the attacker's identity to the account of a signed-in victim who opened a crafted link, and the attacker could then sign in as the victim through OpenID login, which does not apply the local TOTP or WebAuthn checks. The callback now requires a time-limited state value bound to the user.
gitea.dev <= 28.1.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-97204NoneGitea label deletion across repository and organization IDs
CVE-2026-109553NoneGitea SSH certificate principal impersonation of other users
CVE-2026-107618NoneGitea cross-site request forgery on repository topics
CVE-2026-105661NoneGitea panic on the repositories route of individual users
CVE-2026-110324NoneGitea private profile information disclosure through POST request
CVE-2026-107686NoneGitea reactions accepted on locked issues and comments