CVE-2025-11157 Arbitrary Code Execution in feast-dev/feast
Attackers can execute arbitrary code on Kubernetes worker pods by modifying YAML configuration files due to unsafe deserialization in Feast.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-11157?
CVE-2025-11157 is a high-severity unsafe deserialization vulnerability in feast-dev/feast, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
A high-severity remote code execution vulnerability exists in feast-dev/feast version 0.53.0, specifically in the Kubernetes materializer job located at `feast/sdk/python/feast/infra/compute_engines/kubernetes/main.py`. The vulnerability arises from the use of `yaml.load(..., Loader=yaml.Loader)` to deserialize `/var/feast/feature_store.yaml` and `/var/feast/materialization_config.yaml`. This method allows for the instantiation of arbitrary Python objects, enabling an attacker with the ability to modify these YAML files to execute OS commands on the worker pod. This vulnerability can be exploited before the configuration is validated, potentially leading to cluster takeover, data poisoning, and supply-chain sabotage.
Weakness: CWE-502
Which versions are affected by CVE-2025-11157?
3 open source packages ship an affected version, including feast.
| Package | Affected | Fixed in |
|---|---|---|
feast PyPI | All versions | 0.54.0 |
feast PyPI | All versions | 0.54.0 |
feast PyPI | All versions | 0.54.0 |
How do I fix CVE-2025-11157?
Upgrade feast to 0.54.0 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-11157 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11157 exists.
Sources
Also known as GHSA-34wm-4hw7-qfjv, PYSEC-2026-1366.