# CVE-2026-33075: FastGPT has Arbitrary Code Execution in GitHub Actions via pull_request_target in fastgpt-preview-image.yml

> External contributors can execute arbitrary code and steal secrets via a vulnerable GitHub Actions workflow in FastGPT.

- **Severity:** Critical 9.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-xfx8-w35j-485c

## What is CVE-2026-33075?

CVE-2026-33075 is a critical code injection vulnerability in labring FastGPT, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-33075?

It affects 1 product.


Products: Fastgpt Fastgpt.

## How do I fix CVE-2026-33075?

No fix has been published for CVE-2026-33075 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33075 being exploited?

There is no known exploitation of CVE-2026-33075 in the wild and no public exploit code.

Public exploit code:

- Security-research lab: controlled reproduction of CVE-2026-33075 (pwn request in labring/FastGPT preview-image workflow, pull_request_target + checkout-of-fork + privileged buildx push) (github_poc): https://github.com/pvharmo2/gha-lab-61c59f4acb

## Other vulnerabilities in labring FastGPT

- [CVE-2026-34162](https://insights.sbomify.com/CVE-2026-34162/): FastGPT: Unauthenticated SSRF via httpTools Endpoint Leads to Internal API Key Theft (critical 10.0)
- [CVE-2026-40351](https://insights.sbomify.com/CVE-2026-40351/): FastGPT: NoSQL Injection in loginByPassword leads to Authentication Bypass (critical 9.8)
- [CVE-2026-40352](https://insights.sbomify.com/CVE-2026-40352/): FastGPT: NoSQL Injection in updatePasswordByOld Leads to Account Takeover (high 8.8)
- [CVE-2026-34163](https://insights.sbomify.com/CVE-2026-34163/): Server-Side Request Forgery via MCP Tools Endpoint in FastGPT (high 7.7)
- [CVE-2026-26075](https://insights.sbomify.com/CVE-2026-26075/): Cross-Site Request Forgery (CSRF) in FastGPT (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33075 and fix it if it is affected.

What it is: CVE-2026-33075 is a critical code injection vulnerability in labring FastGPT, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33075 in the wild and no public exploit code.

Affected product: labring FastGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33075/ (Markdown: https://insights.sbomify.com/CVE-2026-33075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33075
- OSV: https://osv.dev/vulnerability/CVE-2026-33075

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33075/
Summaries are generated and may contain mistakes; the official description above is the record.