← Back
CVE-2026-25726
high
CVSS 8.1
Vulnerability in github.com/cloudreve/Cloudreve (CVE-2026-25726)
Summary
vulnerability in github.com/cloudreve/Cloudreve (CVE-2026-25726). Successful exploitation can lead to full system takeover. Exploitable via ``secret_key``. Mitigation: upgrade to `4.0.0-20260205113604-ec9fdd33bc54` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25726** has been found in github.com/cloudreve/Cloudreve.
Attackers can target a specific entry point like ``secret_key`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade github.com/cloudreve/Cloudreve to **4.0.0-20260205113604-ec9fdd33bc54** or later.
If unsure, ask your IT team or search "github.com/cloudreve/Cloudreve CVE-2026-25726" on the vendor's site.
CVE-2026-25726 (github.com/cloudreve/Cloudreve) — CWE-338 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `secret_key` / `hash_id_salt`
Patched: `4.0.0-20260205113604-ec9fdd33bc54` — 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-338) exists in github.com/cloudreve/Cloudreve. Attackers reach the vulnerable code path via ``secret_key`` without authentication.
📍 Affected scope
github.com/cloudreve/Cloudreve — . Attack surface: `secret_key` / `hash_id_salt`.
🔥 Severity
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.0.0-20260205113604-ec9fdd33bc54**.
🛡️ 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 'github.com/cloudreve/Cloudreve' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/cloudreve/Cloudreve' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/cloudreve/Cloudreve` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/cloudreve/Cloudreve to 4.0.0-20260205113604-ec9fdd33bc54ステージング環境で 4.0.0-20260205113604-ec9fdd33bc54 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/cloudreve/Cloudreve
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/cloudreve/Cloudreve/v3
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go
github.com/cloudreve/Cloudreve/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.0.0-20260205113604-ec9fdd33bc54"}]}]