Gitea 安全设置中的 OpenID 关联回调在接收 OpenID 2.0 断言时,未验证当前已登录用户是否主动发起了该关联操作。由于 OpenID 2.0 允许非请求(unsolicited)的断言,攻击者可控制的 OpenID 提供者能够将攻击者身份绑定到已登录受害者(点击了恶意构造链接)的账户上。随后,攻击者可通过 OpenID 登录冒充该受害者,而该登录流程不会执行本地 TOTP 或 WebAuthn 验证。修复后,该回调现要求携带与用户绑定的、有时效限制的 值。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-109553 | Gitea SSH certificate principal impersonation of other users | |
| CVE-2026-105661 | Gitea panic on the repositories route of individual users | |
| CVE-2026-105964 | Gitea Actions artifact v4 API unbounded request body | |
| CVE-2026-109844 | Gitea watched repositories API disclosure after access revocation | |
| CVE-2026-107618 | Gitea cross-site request forgery on repository topics | |
| CVE-2026-107686 | Gitea reactions accepted on locked issues and comments | |
| CVE-2026-110494 | Gitea release attachment re-linking of issue attachments | |
| CVE-2026-110324 | Gitea private profile information disclosure through POST request | |
| CVE-2026-110311 | Gitea draft release creation disclosing attachment metadata | |
| CVE-2026-97204 | Gitea label deletion across repository and organization IDs | |
| CVE-2026-97859 | Gitea API disclosure of private user social graph, keys and stars |
No comments yet