Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-54562 medium CVSS 6.5

SSRF (Server-Side Request Forgery) in github.com/cloudreve/Cloudreve/v4 (CVE-2026-54562)

Summary

SSRF in github.com/cloudreve/Cloudreve/v4 (CVE-2026-54562). Confidential information can be exposed externally. Exploitable via `POST /api/v4/workflow/download`. Mitigation: upgrade to `4.0.0-20260606025411-aaebf317a78f` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-54562** has been found in github.com/cloudreve/Cloudreve/v4. Attackers can target a specific entry point like `POST /api/v4/workflow/download` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 6.5/10. What to do: upgrade github.com/cloudreve/Cloudreve/v4 to **4.0.0-20260606025411-aaebf317a78f** or later. If unsure, ask your IT team or search "github.com/cloudreve/Cloudreve/v4 CVE-2026-54562" on the vendor's site.
CVE-2026-54562 (github.com/cloudreve/Cloudreve/v4) — CWE-918 / CVSS v3 6.5 Attack vector: remote (network-reachable) / no user interaction Attack surface: POST /api/v4/workflow/download / GET /api/v4/workflow / GET /api/v4/file / POST /api/v4/file/url Patched: `4.0.0-20260606025411-aaebf317a78f` — 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
**SSRF** (CWE-918) exists in github.com/cloudreve/Cloudreve/v4. Attackers reach the vulnerable code path via `POST /api/v4/workflow/download` without authentication.
📍 Affected scope
github.com/cloudreve/Cloudreve/v4 — . Attack surface: POST /api/v4/workflow/download / GET /api/v4/workflow / GET /api/v4/file / POST /api/v4/file/url.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.0.0-20260606025411-aaebf317a78f**.
🛡️ 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 `POST /api/v4/workflow/download` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/cloudreve/Cloudreve/v4' .` 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/cloudreve/Cloudreve/v4' . | grep -v node_modules

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

  2. 3
    Hunt for indicators of compromise detect 
    grep 'POST /api/v4/workflow/download' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `POST /api/v4/workflow/download` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch 
    Upgrade github.com/cloudreve/Cloudreve/v4 to 4.0.0-20260606025411-aaebf317a78f

    ステージング環境で 4.0.0-20260606025411-aaebf317a78f に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Replay attack against POST /api/v4/workflow/download on staging to confirm patch closes the vector

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

Affected packages

go github.com/cloudreve/Cloudreve/v4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-20260606025411-aaebf317a78f"}]}]
go github.com/cloudreve/Cloudreve/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →