CVE-2026-109553 json
Gitea SSH certificate principal impersonation of other users
published 2026-10-18 21 d ago modified 2026-11-02 6 d ago also EUVD-2026-103983
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/go-gitea/gitea#39839 pull request
- github.com/go-gitea/gitea#39847 pull request
- github.com/go-gitea/gitea/releases/tag/v28.2.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 20 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Gitea Gitea
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/go-gitea/gitea/pull/39839
patch
-
github.com
/go-gitea/gitea/pull/39847
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-vcp6-2qc6-gvq3
vendor-advisory
-
blog.gitea.com
/release-of-28.2.0/
release-notes
-
github.com
/go-gitea/gitea/releases/tag/v28.2.0
release-notes
Sources
- CVE List CVE-2026-109553
- NVD CVE-2026-109553
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.