Security readout for executives and security teams
Plain-English summary
Feast Kubernetes materializer jobs may run attacker-controlled code if trusted YAML configuration files are modified. This is serious because the worker pod handles feature materialization and may have access to data, credentials, or cluster resources.
Executive priority
Prioritize systems where Feast runs in Kubernetes with access to sensitive ML data or cluster credentials. This is not confirmed as exploited, but the impact can include worker compromise, data poisoning, and broader operational disruption.
Technical view
CVE-2025-11157 is unsafe deserialization in feast-dev/feast 0.53.0. The Kubernetes materializer loads feature_store.yaml and materialization_config.yaml with yaml.load and yaml.Loader before validation, allowing arbitrary Python object instantiation and code execution if an attacker can alter those files.
Likely exposure
Exposure is most likely in Kubernetes deployments using Feast materializer jobs where users, pipelines, mounted volumes, or configuration systems can modify the two YAML files. The bundle does not identify all affected versions beyond 0.53.0.
Exploitation context
The provided CVSS vector is local, low complexity, low privilege, and no user interaction. No KEV listing is provided, and the source bundle does not confirm active exploitation. Abuse requires write access to the relevant YAML configuration files.
Researcher notes
The core issue is CWE-502 unsafe deserialization before config validation. Validation should focus on the Kubernetes materializer path and control over /var/feast/feature_store.yaml and /var/feast/materialization_config.yaml. Avoid assuming remote unauthenticated exploitation.
Mitigation direction
- Apply vendor fixes referenced by the Feast commit and Red Hat advisory.
- Restrict write access to Feast materializer configuration files and backing volumes.
- Review Kubernetes RBAC for users and workloads that can alter materializer job inputs.
- Treat feature-store configuration changes as privileged, reviewed deployment changes.
- If no fixed package is available, follow Feast and Red Hat guidance.
Validation and detection
- Inventory Feast deployments and identify Kubernetes materializer usage.
- Check for feast-dev/feast version 0.53.0 in images and dependencies.
- Review who can modify feature_store.yaml and materialization_config.yaml.
- Inspect Kubernetes audit logs for unexpected materializer configuration changes.
- Confirm deployed code no longer uses unsafe yaml.Loader for these files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-11157 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9@huntr_aiCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.0 score
7.8HighVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-01T08:00:48.932Z: Reported to Red Hat.
- 2026-01-01T07:03:57.277Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://huntr.com/bounties/46d4d585-b968-4a76-80ce-872bc5525564CVE reference, @huntr_ai
- https://github.com/feast-dev/feast/commit/b2e37ff37953b68ae833f6874ab5bc510a4ca5fbCVE reference, @huntr_ai
- https://access.redhat.com/security/cve/CVE-2025-11157CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2426574CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-11157.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:10184CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.