Open Redirect in Nezha (CVE-2026-111385)
Summary
Vulnerability in Nezha (CVE-2026-111385). Risk of unauthorized operations or information disclosure. Exploitable via Host header.
Original description
The description as published by the source.
Nezha from 2.1.0 before 2.3.15 contains a host header injection vulnerability in mintTransferTool that builds fs.download_url and fs.upload_url transfer URLs from the unvalidated Host header. Attackers who control the Host header seen on a victim's MCP request can redirect file uploads or capture one-time download tokens and replay them to exfiltrate files.
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-111385 has been found in Nezha.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Nezha CVE-2026-111385" on the vendor's site.
CVE-2026-111385 (Nezha) — CWE-601 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host header
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.
A vulnerability (CWE-601) exists in Nezha. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of Nezha. Attack surface: Host header.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Nezha' . 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
-
1Identify exposure identify
grep -r 'Nezha' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Nezhaを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。