CVE-2026-55563
- Source
- https://cve.org/CVERecord?id=CVE-2026-55563
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-55563.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-55563
- Aliases
-
- GHSA-2j2x-r73g-hrr5
- Published
- 2026-09-21T15:51:06Z
- Modified
- 2026-09-23T03:47:18Z
- Severity
-
- 8.9 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVSS Calculator
- Summary
- Feast: `pull_request_target` integration tests run untrusted fork code with production cloud secrets; the `ok-to-test` label guard is bypassable via label persistence on `synchronize`
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-863" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55563.json" }- References
-
- https://github.com/feast-dev/feast/releases/tag/v0.65.0
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55563.json
- https://github.com/feast-dev/feast/security/advisories/GHSA-2j2x-r73g-hrr5
- https://nvd.nist.gov/vuln/detail/CVE-2026-55563
- https://github.com/feast-dev/feast/commit/76192229eca01661109ed56e0dd0cf8f732975f6