VulnerabilityPublished 10 Feb 2026

CVE-2026-26003: labring FastGPT · Open Redirect

Affects labring FastGPTSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.14.5-fix when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.14.5-fix

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Subsequent System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Subsequent System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade labring FastGPT to 4.14.5-fix.

Affected software

Product	Affected	Fixed in
labringFastGPT	Affected >=4.14.0 <4.14.5-fix	Fixed in 4.14.5-fix

AI-suggested

European organizations should immediately upgrade FastGPT to version 4.14.5-fix or later to remediate this vulnerability. Until patching is complete, network-level controls such as web application firewalls (WAFs) should be configured to restrict access to the FastGPT/api/plugin/ endpoints, allowing only trusted IP addresses or internal network segments. Monitoring and alerting should be enhanced for unusual API access patterns or plugin system crashes. Organizations should review plugin usage and backup plugin installation states regularly to enable rapid recovery if crashes occur. Security teams should educate users about phishing risks related to open redirects and implement email filtering to detect malicious URLs. Additionally, organizations should conduct penetration testing focused on API endpoints to identify similar vulnerabilities. Vendor communication channels should be monitored for further updates or patches. Finally, consider isolating FastGPT instances in segmented network zones to limit exposure.

Description

FastGPT is an AI Agent building platform. From 4.14.0 to 4.14.5, attackers can directly access the plugin system through FastGPT/api/plugin/xxx without authentication, thereby threatening the plugin system. This may cause the plugin system to crash and the loss of plugin installation status, but it will not result in key leakage. For older versions, as there are only operation interfaces for obtaining information, the impact is almost negligible. This vulnerability is fixed in 4.14.5-fix.

Impact

For European organizations using FastGPT versions between 4.14.0 and 4.14.5-fix, this vulnerability could disrupt AI agent operations by crashing the plugin system and causing loss of plugin installation status, potentially impacting business processes relying on these AI agents. Although no direct data leakage or key compromise occurs, the denial of service effect could degrade service availability and reliability. Organizations integrating FastGPT into critical workflows may experience operational interruptions. Additionally, the open redirect aspect could be abused in phishing campaigns targeting employees or partners, increasing the risk of social engineering attacks. The impact is more significant for organizations with heavy reliance on AI automation and plugin extensibility. However, since exploitation requires no authentication and no user interaction, the attack surface is broad, increasing the likelihood of opportunistic attacks. The absence of known exploits reduces immediate risk but does not eliminate it, especially as attackers may develop exploits over time.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 18:32 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats