Gitea resolved the principals of an SSH certificate by searc… (CVE-2026-109553)

Summary

Vulnerability reported (CVE-2026-109553). Risk of unauthorized operations or information disclosure. Exploitable via SSH_TRUSTED_USER_CA_KEYS.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-109553 has been found.
Attackers can target a specific entry point like SSH_TRUSTED_USER_CA_KEYS over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-109553" on the vendor's site.

CVE-2026-109553
Attack surface: SSH_TRUSTED_USER_CA_KEYS
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) has been reported. Attackers reach the vulnerable code path via SSH_TRUSTED_USER_CA_KEYS.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: SSH_TRUSTED_USER_CA_KEYS.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Gitea resolved the principals of an SSH certificate by searching the content of all stored public keys instead of only…

Summary

Original description

Auto-generated summary

Response actions

References