Skip to main content
VulnerabilityPublished

CVE-2026-33075: labring FastGPT · Download of Code Without Integrity Check

Affects labring FastGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
labringFastGPTAffected
  • <=4.14.8.3
Fixed in–
GitHublabring/FastGPTpkg:github/labring/FastGPTOther threatsAffected
  • <=4.14.8.3
Fixed in–

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

AI-suggested

To mitigate this vulnerability, organizations should immediately audit their use of GitHub Actions workflows, especially those triggered by pull_request_target events that access repository secrets. Avoid checking out code from untrusted forks in workflows with elevated privileges. Instead, separate workflows that require secrets from those that build untrusted code, or use pull_request events without access to secrets for untrusted code. Implement strict code review policies and restrict who can submit pull requests that trigger privileged workflows. Use ephemeral or limited-scope secrets and rotate them regularly. Monitor container registries for unexpected image pushes and implement image signing and verification to detect tampering. Until an official patch is released, consider disabling or restricting the vulnerable workflow. Employ runtime security controls to detect anomalous container behavior. Finally, stay updated with vendor advisories for patches and apply them promptly once available.

Description

FastGPT is an AI Agent building platform. In versions 4.14.8.3 and below, the fastgpt-preview-image.yml workflow is vulnerable to arbitrary code execution and secret exfiltration by any external contributor. It uses pull_request_target (which runs with access to repository secrets) but checks out code from the pull request author's fork, then builds and pushes Docker images using attacker-controlled Dockerfiles. This also enables a supply chain attack via the production container registry. A patch was not available at the time of publication.

References

Community reviews

Loading reviews…