Critical Vulnerability Exposes Docker Image Supply Chain in GitHub Actions Workflows

A critical vulnerability, identified as CVE-2026-50562, has been disclosed, revealing a severe security flaw in FastGPT's GitHub Actions workflows that could lead to arbitrary code execution through manipulated Docker images. Specifically, the vulnerability resides in the way untrusted pull request (PR) code can build artifacts, including Docker images, which are then processed by privileged workflow_run jobs. This allows an attacker to push malicious Docker images to GitHub Container Registry (GHCR) and subsequently deploy them into Kubernetes environments, leveraging credentials like `KUBE_CONFIG_CN`. The affected FastGPT commits are 22ebfacbb43311e9b73294040ae0eb87390c6bba and earlier. This vulnerability is highly significant for any organization utilizing Docker images within their CI/CD pipelines, particularly those integrated with GitHub Actions and deploying to Kubernetes. It represents a direct and potent supply chain attack vector. The ability for untrusted code to introduce malicious images into a trusted registry and then facilitate their deployment means that the integrity of an entire application ecosystem can be compromised. For practitioners, this translates to risks of unauthorized code execution, severe data breaches, and potential service disruption. Furthermore, such compromises can lead to non-compliance with stringent data protection regulations like GDPR and HIPAA due to unauthorized access or data exposure. The critical CVSS score of 9.3 underscores the severity and potential impact of this flaw. This incident fits squarely within the broader, escalating trend of software supply chain attacks that have plagued the industry in recent years, from high-profile events like SolarWinds to numerous package manager compromises (e.g., npm, PyPI). As organizations increasingly adopt cloud-native architectures and automate their development and deployment processes through CI/CD pipelines, the attack surface expands significantly. Container images, being fundamental building blocks of modern applications, become prime targets. The reliance on automated workflows, while boosting efficiency, also introduces a need for rigorous security checks at every stage, especially when dealing with external contributions or untrusted inputs. This vulnerability highlights the persistent challenge of ensuring the provenance and integrity of software components throughout their lifecycle. In practice, this disclosure means that DevOps and security teams must immediately review and harden their GitHub Actions workflows, especially those that build and push Docker images based on pull requests. Concrete actions include implementing stricter validation for all incoming code, particularly from external contributors, and ensuring that privileged workflows only process artifacts from trusted, verified sources. Organizations should consider rebuilding deployable images from trusted code within privileged workflows rather than directly using PR artifacts. Restricting registry push and Kubernetes deployment permissions to the absolute minimal required scopes is also crucial. Furthermore, robust image scanning for vulnerabilities and malicious content, coupled with image signing, becomes even more imperative to detect and prevent the deployment of compromised images. Practitioners should also evaluate their existing access controls and audit logs for any signs of suspicious activity related to image pushes or Kubernetes deployments.