Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54481 high CVSS 7.5

Vulnerability in code.gitea.io/gitea (CVE-2026-54481)

Summary

Vulnerability in code.gitea.io/gitea (CVE-2026-54481). Successful exploitation can lead to full system takeover. Exploitable via Host header. Mitigation: upgrade to 1.27.0 or later.

Original description

The description as published by the source.

Summary

Gitea's internal API HTTP client (modules/private/internal.go) hardcodes
TLSClientConfig.InsecureSkipVerify = true with no configuration override. It is the only
outbound TLS client in the codebase that cannot be made to verify its peer's certificate —
webhook, migrations, MinIO, LDAP, SMTP, Redis and incoming-mail all expose a secure-by-default
SkipVerify toggle, this one does not.

When an operator configures internal communication over HTTPS to a non-loopback target
(LOCAL_ROOT_URL=https:/// in a split-host / multi-pod topology), the gitea serv / gitea hook
subprocess that calls the internal API will accept ANY TLS certificate. An attacker with on-path
position on that internal segment can MITM the connection and capture the static high-privilege
INTERNAL_TOKEN, which is the sole authentication for every /api/internal/* endpoint (server
shutdown/restart, SSH key authorization, git command execution, repo hooks, mail send, runner-token
generation).

Severity is deployment-dependent: High for split-host HTTPS deployments; Low/Informational for the
default single-host / unix-socket / HTTP-loopback deployment, where the call is loopback and not
interceptable without local access (which already exposes the token directly). This report is
rated for the affected configuration and the underlying defense-in-depth defect.
Details

Affected component: modules/private/internal.go

The internal API transport hardcodes certificate-verification bypass:

var internalAPITransp…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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-54481 has been found in code.gitea.io/gitea.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade code.gitea.io/gitea to 1.27.0 or later.
If unsure, ask your IT team or search "code.gitea.io/gitea CVE-2026-54481" on the vendor's site.

CVE-2026-54481 (code.gitea.io/gitea) — CWE-295 / CVSS v3 7.5
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: Host header
Patched: 1.27.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.

❓ What is the problem

A vulnerability (CWE-295) exists in code.gitea.io/gitea. Attackers reach the vulnerable code path via Host header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of code.gitea.io/gitea. Attack surface: Host header.

🔥 Severity

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

🔧 How to fix

Update to 1.27.0.

🛡️ 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 'code.gitea.io/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 'code.gitea.io/gitea' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade code.gitea.io/gitea to 1.27.0

    ステージング環境で 1.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go code.gitea.io/gitea
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.27.0"}]}]
Go gitea.dev
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.27.0"}]}]

References

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