Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-50562

CRITICAL · 9.3 CVSS v4.0 Published 2026-07-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click 5 weeks old

Official description

NVD · unedited

FastGPT is a knowledge-based AI application platform. At commit 22ebfacbb43311e9b73294040ae0eb87390c6bba and earlier, artifacts built from untrusted pull request code in .github/workflows/preview-docs-build.yml and .github/workflows/preview-fastgpt-build.yml can be downloaded by privileged workflow_run jobs in .github/workflows/preview-docs-push.yml and .github/workflows/preview-fastgpt-push.yml, allowing attacker-controlled Docker images from the document/ tree or FastGPT build context to be pushed to GHCR and, for documentation previews, deployed with secrets.KUBE_CONFIG_CN.

Technical summary

dbcve analysis · high confidence

FastGPT's GitHub Actions CI/CD pipeline allows untrusted pull request artifacts from .github/workflows/preview-docs-build.yml and .github/workflows/preview-fastgpt-build.yml to be downloaded by privileged workflow_run jobs, enabling attackers to inject malicious Docker images that get pushed to GHCR and, for documentation previews, deployed with Kubernetes credentials (KUBE_CONFIG_CN).

MitigationRemove or secure the workflow_run trigger that downloads untrusted PR artifacts, implement artifact verification/signing, and avoid deploying PR preview images with production credentials like KUBE_CONFIG_CN.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
Authentication: X
User interaction: None
Scope: X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify vulnerable workflow files

Check if .github/workflows/preview-docs-build.yml and/or .github/workflows/preview-fastgpt-build.yml exist in the repository root

Affected if Either or both of these workflow files exist in the repository
Verify workflow_run trigger usage

Inspect both workflow files for 'workflow_run' trigger and examine whether they download artifacts using actions like 'download-artifact' from the triggered run

Affected if The workflow uses workflow_run trigger AND downloads artifacts from the untrusted PR workflow run
Check for Kubernetes credential usage

Search both workflow files for references to KUBE_CONFIG_CN, KUBECONFIG, or kubernetes-related secrets/environment variables

Affected if KUBE_CONFIG_CN or similar Kubernetes credentials are used in these workflows
Confirm GHCR image push configuration

Examine the workflows for 'docker build-push-action' or similar steps that push container images to GHCR (ghcr.io)

Affected if The workflows build and push Docker images to GHCR from PR-triggered artifact outputs
Assess artifact trust boundary

Review whether the workflows implement any artifact verification, checksum validation, or signing mechanism before using downloaded artifacts

Affected if No artifact verification or trust validation is implemented before using downloaded PR artifacts

A user is affected if their FastGPT repository contains the preview-docs-build.yml or preview-fastgpt-build.yml workflows that use workflow_run to download untrusted PR artifacts and deploy them with KUBE_CONFIG_CN or push them to GHCR without verification.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Remove or secure the workflow_run trigger that downloads untrusted PR artifacts, implement artifact verification/signing, and avoid deploying PR preview images with production credentials like KUBE_CONFIG_CN.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,800

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-50562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

github.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50562 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-50562?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.3 Critical

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 16 hrs · Moderate

Typical engagement from $2,800

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-50562 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References