Code Injection in FastGPT (CVE-2026-44287)
Summary
Code injection in FastGPT (CVE-2026-44287). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.15.0-beta1 or later.
Original description
The description as published by the source.
FastGPT is an AI Agent building platform. Prior to 4.15.0-beta1, the JavaScript sandbox worker at projects/code-sandbox/src/pool/worker.ts:356 blocks dynamic import() with the regex /\bimport\s*(/.test(code). JavaScript syntax accepts a block comment between import and (; the regex matches only ASCII whitespace, and the bytes /, *, *, / are not in the \s character class. The payload import/**/("child_process") parses as a syntactically valid dynamic import that the regex does not detect. Because import() is not wrapped by the safeRequire Proxy (which only proxies require), the attacker loads child_process and calls execSync - arbitrary command execution as uid=100(sandbox) inside the sandbox container. This vulnerability is fixed in 4.15.0-beta1.
Source: NIST National Vulnerability Database 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-44287 has been found in FastGPT.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade FastGPT to 4.15.0-beta1 or later.
If unsure, ask your IT team or search "FastGPT CVE-2026-44287" on the vendor's site.
CVE-2026-44287 (FastGPT) — CWE-94 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.15.0-beta1 — 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.
Arbitrary code execution (CWE-94) exists in FastGPT.
Check the vendor advisory for the affected versions of FastGPT.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 4.15.0-beta1.
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 'FastGPT' . 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 'FastGPT' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FastGPTを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade FastGPT to 4.15.0-beta1ステージング環境で 4.15.0-beta1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov