Skip to main content
VulnerabilityPublished

CVE-2025-49131: labring FastGPT · Incorrect Permissions

Affects labring FastGPTSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.9.11 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.9.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade labring/FastGPT to 4.9.11.

Affected software

ProductAffectedFixed in
GitHublabring/FastGPTpkg:github/labring/FastGPTOther threatsAffected
  • <4.9.11
Fixed in
  • 4.9.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade FastGPT to version 4.9.11 or later to benefit from the patched syscall restrictions and enhanced sandbox isolation. Beyond upgrading, organizations should implement strict network segmentation and access controls around FastGPT deployment environments to limit exposure. Employ runtime monitoring and anomaly detection focused on syscall patterns and container escape attempts to detect exploitation attempts early. Restrict privileges of FastGPT processes and sandbox containers using Linux security modules (e.g., SELinux, AppArmor) and container security best practices to minimize the blast radius if exploitation occurs. Conduct regular code audits and penetration testing on AI workflow environments to identify potential sandbox bypasses or misconfigurations. Additionally, organizations should maintain up-to-date incident response plans tailored to AI platform compromises and ensure logging of sandbox activity for forensic analysis. Finally, educating developers and operators on secure sandbox usage and the risks of permissive syscall policies will help prevent similar vulnerabilities.

Description

FastGPT 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.

References

Community reviews

Loading reviews…