The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and…
Summary
Vulnerability reported (CVE-2026-110324). Risk of unauthorized operations or information disclosure. Exploitable via POST /{username}. Mitigation: upgrade to 28.1.0 or later.
Original description
The description as published by the source.
The visibility check of Gitea user profiles was applied to GET requests only, while POST /{username} (follow and unfollow) required only a signed-in user. Any authenticated user could therefore obtain the full name, location, website and description of a user with a private profile from the response. The issue was fixed in 28.1.0 and disclosed with 28.2.0.
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-110324 has been found.
Attackers can target a specific entry point like POST /{username} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade the affected software to 28.1.0 or later.
If unsure, ask your IT team or search "CVE-2026-110324" on the vendor's site.
CVE-2026-110324 — CWE-200
Attack surface: POST /{username}
Patched: 28.1.0 — apply immediately
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.
Information disclosure (CWE-200) has been reported. Attackers reach the vulnerable code path via POST /{username}.
Check the vendor advisory for the affected versions. Attack surface: POST /{username}.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 28.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /{username} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'POST /{username}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /{username}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade to 28.1.0ステージング環境で 28.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /{username} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web blog.gitea.com
- web github.com
- web github.com
- web github.com
- web github.com