Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-42343: CWE-400: Uncontrolled Resource Consumption in labring FastGPT

0
Medium
VulnerabilityCVE-2026-42343cvecve-2026-42343cwe-400
Published: Fri May 08 2026 (05/08/2026, 22:09:03 UTC)
Source: CVE Database V5
Vendor/Project: labring
Product: FastGPT

Description

CVE-2026-42343 is a medium severity vulnerability in labring FastGPT versions 4. 14. 13 and earlier. The code-sandbox component lacks sufficient resource isolation and relies only on a soft application-level memory limit, allowing attackers to bypass memory checks and exhaust CPU resources. This can lead to a Denial of Service (DoS) condition, preventing legitimate users from accessing the service. No official patch or remediation is available at the time of publication.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/08/2026, 22:37:01 UTC

Technical Analysis

FastGPT, an AI Agent building platform by labring, suffers from uncontrolled resource consumption in its code-sandbox component in versions up to 4.14.13. The vulnerability arises because the service uses only a 500ms polling interval as a soft limit for memory management without enforcing strict OS-level resource constraints such as cgroups or kernel namespaces. Attackers can exploit this design by launching concurrent CPU-intensive requests or timing attacks to bypass memory checks, exhausting the JavaScript worker pool and causing a complete Denial of Service.

Potential Impact

Successful exploitation results in a Denial of Service, where legitimate users are unable to use FastGPT due to resource exhaustion. The vulnerability does not require privileges or user interaction and can be exploited remotely over the network. There are no known exploits in the wild at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider implementing external resource limits at the OS or container level to mitigate risk. Monitoring and limiting concurrent CPU-intensive requests may help reduce impact but are not guaranteed to fully prevent exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-26T13:26:14.514Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69fe61e5cbff5d8610367faf

Added to database: 5/8/2026, 10:21:25 PM

Last enriched: 5/8/2026, 10:37:01 PM

Last updated: 5/9/2026, 1:22:44 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses