The vulnerability CVE-2025-11157 affects feast-dev/feast version 0.53.0 and arises from the use of yaml.load(..., Loader=yaml.Loader) to deserialize untrusted YAML configuration files (/var/feast/feature_store.yaml and /var/feast/materialization_config.yaml) in the Kubernetes materializer job. This unsafe deserialization allows instantiation of arbitrary Python objects, enabling remote code execution if an attacker can modify these YAML files before validation. The vulnerability has a CVSS 3.0 score of 7.8 with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating it requires local access with low complexity and privileges but results in high confidentiality, integrity, and availability impact. Red Hat has published advisories acknowledging this vulnerability. However, no explicit patch or fix is detailed in the advisory content provided.

Successful exploitation allows an attacker with the ability to modify specific YAML configuration files to execute arbitrary OS commands on the Kubernetes worker pod running feast-dev/feast. This can lead to full cluster takeover, data poisoning, and supply-chain sabotage, severely compromising confidentiality, integrity, and availability of the affected environment.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The Red Hat advisories acknowledge the vulnerability but do not explicitly state a fixed version or patch availability. Until a patch is released, restrict access to the YAML configuration files to trusted users only and avoid running feast-dev/feast version 0.53.0 in untrusted environments. Monitor vendor channels for updates and apply official fixes once available.