dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-44287

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FastGPT JavaScript sandbox worker uses a flawed regex /\bimport\s*\(/ to block dynamic import() calls, but this regex only matches ASCII whitespace (\s) and can be bypassed using block comments like import/**/("child_process"). This allows attackers to load the child_process module and execute arbitrary commands via execSync as the sandbox user (uid=100).

MitigationUpgrade to FastGPT version 4.15.0-beta1 or later, which implements proper handling of dynamic import() and blocks the child_process module access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FastGPT installation
    Locate the FastGPT installation directory and check for package.json or version configuration files. Common paths include the deployment directory or Docker container.
    Affected if FastGPT is not installed - the system is not affected.
  2. Determine installed FastGPT version
    Read the version from package.json, a version file, or run a command like 'npm list fastgpt' or 'docker ps' to inspect the container image tag.
    Affected if The installed version is earlier than 4.15.0-beta1 (such as 4.14.x, 4.13.x, or earlier).
  3. Confirm sandbox worker is in use
    Check if the FastGPT deployment uses the JavaScript sandbox worker feature, which is typically enabled by default for code execution capabilities.
    Affected if The sandbox worker is enabled and running to process dynamic code requests.
  4. Verify regex protection exists
    Inspect the sandbox worker source code for the regex pattern /\bimport\s*\(/ and confirm it only uses ASCII whitespace matching (\s), not Unicode-aware whitespace.
    Affected if The regex only matches ASCII \s and does not account for block comments between 'import' and '('.

A user is affected if FastGPT version is earlier than 4.15.0-beta1 and the sandbox worker with the vulnerable regex is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FastGPT version 4.15.0-beta1 or later, which implements proper handling of dynamic import() and blocks the child_process module access.

Recommended fix High confidence

4.15.0-beta1

  1. Upgrade FastGPT to version 4.15.0-beta1 or later
  2. Verify the upgrade was successful by checking the version number
  3. Test that the sandbox properly blocks dynamic imports including those with block comments like import/**/()
Caveat This is a beta version upgrade; review beta release notes for any other changes before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44287 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data