Gitea 在解析 SSH 证书的主体(principals)时,错误地遍历了所有已存储的公钥内容,而本应仅检查专门用于主体的密钥。当 Gitea 配置为信任用户证书颁发机构( )并允许任意主体( )时,攻击者可以将其他用户的公钥行注册为自己的主体,或者持有由该机构签发的证书的用户也可以列出该公钥,随后通过 HTTP 签名 API 及内置 SSH 服务器冒充该公钥的拥有者进行身份验证。未配置信任用户证书颁发机构的实例不受此问题影响。
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-104627 | Gitea OpenID account linking without session binding | |
| 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