← Back
CVE-2026-40346
medium
CVSS 6.5
SSRF (Server-Side Request Forgery) in @nocobase/plugin-workflow-request (CVE-2026-40346)
Summary
SSRF in @nocobase/plugin-workflow-request (CVE-2026-40346). Confidential information can be exposed externally. Exploitable via ``url``. Mitigation: upgrade to `2.0.37` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-40346** has been found in @nocobase/plugin-workflow-request.
Attackers can target a specific entry point like ``url`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade @nocobase/plugin-workflow-request to **2.0.37** or later.
If unsure, ask your IT team or search "@nocobase/plugin-workflow-request CVE-2026-40346" on the vendor's site.
CVE-2026-40346 (@nocobase/plugin-workflow-request) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `url`
Patched: `2.0.37` — 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 @nocobase/plugin-workflow-request. Attackers reach the vulnerable code path via ``url`` without authentication.
📍 Affected scope
@nocobase/plugin-workflow-request — . Attack surface: `url`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.0.37**.
🛡️ 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 '@nocobase/plugin-workflow-request' .` 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 '@nocobase/plugin-workflow-request' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@nocobase/plugin-workflow-request` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @nocobase/plugin-workflow-request to 2.0.37ステージング環境で 2.0.37 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@nocobase/plugin-workflow-request
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.37"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-40346
- package https://github.com/nocobase/nocobase
- web https://github.com/nocobase/nocobase/commit/2853368243ed07339c62c548b7d475f4eeaada59
- web https://github.com/nocobase/nocobase/pull/9079
- web https://github.com/nocobase/nocobase/releases/tag/v2.0.37
- web https://github.com/nocobase/nocobase/security/advisories/GHSA-mvvv-v22x-xqwp
- web https://github.com/advisories/GHSA-mvvv-v22x-xqwp