When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked up with an SQL `LIKE` comparison of its encoded content, which is case-insensitive on some databases, including the default SQLite. An attacker who can construct a case variant of another user's registered RSA public key for which they can derive the private key could have that key matched to the victim's account and authenticate over SSH as that user. Keys are now looked up by fingerprint.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39423 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8pwg-hcgm-54cp Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.1 · giteaNVD modified 2026-10-15 02:26
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 4
- https://blog.gitea.com/release-of-28.0.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39423 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8pwg-hcgm-54cp Vendor Advisory