Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only principal keys. When Gitea trusts a user certificate authority (`SSH_TRUSTED_USER_CA_KEYS`) and accepts arbitrary principals (`SSH_AUTHORIZED_PRINCIPALS_ALLOW=anything`), a user could register another user's public key line as their own principal, or a holder of a certificate signed by that authority could list it, and then authenticate as the owner of that key through the HTTP signature API and the built-in SSH server. Instances that do not trust a user certificate authority are not affected.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-19 20:19
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-19 21:17
- CVSS7.5 (v3.1, CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H)NVD modified 2026-10-19 21:17
- First seenunscoredNVD modified 2026-10-18 19:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.