Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71184 high CVSS 8.8

Authorization Flaw in Gitea (CVE-2026-71184)

Summary

Vulnerability in Gitea (CVE-2026-71184). Successful exploitation can lead to full system takeover. Exploitable via pull_request_review_comment.

Original description

The description as published by the source.

Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code from the fork head and run it on the base repository's runners without the required maintainer approval. This allows execution of fork-controlled workflow code across the intended approval boundary.

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-71184 has been found in Gitea.
Attackers can target a specific entry point like pull_request_review_comment over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Gitea CVE-2026-71184" on the vendor's site.

CVE-2026-71184 (Gitea) — CWE-863 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: pull_request_review_comment / WithPullRequest
Affected: >= 1.20.0, <= 1.27.1
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

Incorrect authorization (CWE-863) exists in Gitea. Attackers reach the vulnerable code path via pull_request_review_comment.

📍 Affected scope

Affected versions of Gitea: >= 1.20.0, <= 1.27.1. Attack surface: pull_request_review_comment / WithPullRequest.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory. (If a vulnerable version >= 1.20.0, <= 1.27.1 is in production, plan an immediate maintenance window.)

🛡️ 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. Run grep -r 'Gitea' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'Gitea' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Gitea を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Match against affected range verify 
    Confirm if version satisfies `>= 1.20.0, <= 1.27.1`

    Step 1 で見つかったバージョンが影響範囲 >= 1.20.0, <= 1.27.1 に該当するか照合。本番で稼働中ならインシデント扱い。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details