CVE-2026-55563
Received Received - Intake

Privileged Code Execution in Feast Feature Store

Publication date: 2026-09-21

Last updated on: 2026-09-21

Assigner: GitHub, Inc.

Description
Feast is the open source feature store for AI and machine learning. Prior to 0.65.0, .github/workflows/pr_integration_tests.yml uses pull_request_target with the synchronize event and preserves ok-to-test, approved, or lgtm labels across newly pushed commits, allowing a fork contributor to obtain approval for a benign revision and then run changed code from refs/pull/${{ github.event.pull_request.number }}/merge through privileged make targets. The job exposes GCP, AWS, and Snowflake credentials to that code, enabling runner code execution, credential disclosure, and possible access to downstream cloud resources. An external label-removal integration could mitigate the condition, but no repository workflow provided that protection. This issue is fixed in version 0.65.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-21
Last Modified
2026-09-21
Generated
2026-09-21
AI Q&A
2026-09-21
EPSS Evaluated
N/A
NVD
CVE-2026-55563
EUVD
EUVD-2026-83981

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
feast feast to 0.65.0 (inc)
feast-dev feast 0.65.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Feast, a feature store for AI/ML, involves a GitHub Actions workflow using pull_request_target with synchronize events. It allows untrusted fork contributors to run malicious code in a privileged CI environment with access to cloud credentials like GCP, AWS, and Snowflake secrets. The issue persists because GitHub retains labels like ok-to-test across new commits, enabling attackers to bypass security checks by pushing malicious code after obtaining approval for a benign change.

Detection Guidance

Check GitHub Actions workflows in Feast repositories for the use of pull_request_target with synchronize events. Look for workflows exposing cloud credentials like GCP, AWS, or Snowflake secrets. Verify if labels like ok-to-test, approved, or lgtm persist across new commits in pull requests.

Impact Analysis

If exploited, this vulnerability could lead to remote code execution on the CI runner, disclosure of cloud credentials, and unauthorized access to Feast's cloud infrastructure. Attackers could misuse compute resources, exfiltrate sensitive data, or gain control over downstream cloud services like databases or storage systems.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Exposure of cloud credentials may also result in non-compliance with data handling and access control mandates in these regulations.

Mitigation Strategies

Upgrade to Feast version 0.65.0 or later. Remove synchronize event triggers from pull_request_target workflows. Strip labels on new commits or split pipelines into unprivileged and privileged jobs. Scope secrets to GitHub Environments with required reviewers.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-55563. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart