CVE-2025-49131
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 · uneditedFastGPT is an open-source project that provides a platform for building, deploying, and operating AI-driven workflows and conversational agents. The Sandbox container (fastgpt-sandbox) is a specialized, isolated environment used by FastGPT to safely execute user-submitted or dynamically generated code in isolation. The sandbox before version 4.9.11 has insufficient isolation and inadequate restrictions on code execution by allowing overly permissive syscalls, which allows attackers to escape the intended sandbox boundaries. Attackers could exploit this to read and overwrite arbitrary files and bypass Python module import restrictions. This is patched in version 4.9.11 by restricting the allowed system calls to a safer subset and additional descriptive error messaging.
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 confidenceThe fastgpt-sandbox container before version 4.9.11 contains insufficient isolation due to overly permissive syscalls, allowing attackers to escape the sandbox and read/write arbitrary files on the host system. The vulnerability also enables bypassing Python module import restrictions, giving attackers full execution capabilities beyond the intended isolated environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.9.11CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if fastgpt-sandbox container is deployedCheck your container runtime (Docker, Podman, Kubernetes) for any running or stopped containers named 'fastgpt-sandbox' or using the fastgpt-sandbox imageAffected if No fastgpt-sandbox container found means the vulnerability does not apply to your environment
-
Determine the installed version of fastgpt-sandboxRun 'docker images' or 'podman images' and look for the fastgpt-sandbox image tag, or inspect the container metadata with 'docker inspect <container>' to find the image digest or tagAffected if The version is affected if the image tag or digest corresponds to a release earlier than 4.9.11
-
Check if the sandbox container is runningVerify the container status with 'docker ps -a' or kubectl get pods if running in KubernetesAffected if A running container with an affected version is actively vulnerable; a stopped container poses no immediate risk but is still vulnerable if restarted with the same image
-
Verify the seccomp or syscall restrictions applied to the containerInspect the container's security options using 'docker inspect' under SecurityConfig or check the seccomp profile specified in your container runtime configurationAffected if If no restrictive seccomp profile is enforced or the container runs with overly permissive security settings, the escape is more easily exploitable
Your environment is affected if you have a fastgpt-sandbox container running a version earlier than 4.9.11, regardless of whether the sandbox escape has been actively exploited yet.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.9.11
Upgrade fastgpt-sandbox to version 4.9.11 or later which restricts allowed syscalls to a safer subset. If immediate patching is not feasible, minimize the attack surface by restricting network access to the sandbox and implementing additional monitoring for unauthorized file system access.
Upgrade to FastGPT version 4.9.11 or later (specifically the fastgpt-sandbox component)
- Check current FastGPT version by inspecting the running container or docker-compose.yml file
- Pull the latest FastGPT images, specifically updating to version 4.9.11 or later for both fastgpt and fastgpt-sandbox containers
- Update docker-compose.yml or helm values.yaml to use version 4.9.11 for the sandbox component (fastgpt-sandbox)
- Pull the new container images: docker-compose pull or helm upgrade
- Restart the sandbox container to apply the updated image with restricted syscalls
- Verify the sandbox is running the patched version 4.9.11 or later
- Test that code execution in the sandbox still functions correctly for legitimate use cases
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49131 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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