cve.bz

CVE-2026-56121 feast-dev feast: Deserialization of Untrusted Data

9.3 criticalEPSS 1.4%Fix available

Critical (9.3) in feast-dev feast. EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in feast 0.63.0.

On this page
Feast before 0.63.0 contains an unsafe deserialization vulnerability that allows unauthenticated or unauthorized attackers to achieve remote code execution by sending a crafted gRPC request to the registry server. The user_defined_function.body field of an OnDemandFeatureView spec is decoded from base64 and passed to dill.loads() before any authorization check is performed, enabling attackers to embed a malicious serialized Python object with an arbitrary __reduce__ method to execute OS commands as the feast service account.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 73rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-06-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • feast (PyPI): fixed in 0.63.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-56121 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56121?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56121?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56121 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
feast-dev feastbefore 0.63.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q63x-9pfm-mjx4PyPIfeast<0.63.00.63.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat OpenShift AI ships Feast versions affected by CVE-2026-56121. This flaw allows remote code execution only against the Feast registry gRPC server (feast serve_registry, port 6570) when that service is running and reachable.

Default OpenShift AI installations are not affected. Installing OpenShift AI deploys the Feast operator but does not create a FeatureStore instance or start a registry server. The default FeatureStore configuration runs the online feature server only (feast serve), which does not expose the vulnerable gRPC endpoint. Workbench and pipeline runtime images include Feast as a client library and do not start a registry server.

Red Hat validated this by attempting exploitation against Feast 0.62.0: remote code execution succeeded only when a registry server was explicitly started; the default online-only configuration and library-only images were not exploitable.

Customers who configure a FeatureStore with an explicit registry server (registry.local.server) should treat this as a critical issue and apply the fix (Feast ≥ 0.63.0) when available. Enabling authorization alone does not remediate affected versions because unsafe deserialization occurs before authorization checks.

Red Hat rates this Important for OpenShift AI overall, reflecting that the vulnerable component is present but the attack surface is not exposed under default configurations.

Red Hat's mitigation

- Restrict network access to Feature Server / registry endpoints (NetworkPolicy, Route auth, no public exposure).

- Do not expose the Feast registry gRPC port to untrusted networks; place behind OpenShift Route + platform authentication.

ProductPackageStateAdvisory
Red Hat OpenShift AI 2.25rhoai/odh-feature-server-rhel9:1792148523Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1787073866Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9:1787073873Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1787073459Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9:1787073611Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9:1787073451Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9:1787073451Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:1787121387Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1787074331Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9:1787073605Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9:1787073546Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9:1787073717Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9:1787073713Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-feature-server-rhel9:1791863220Fixed 2026-10-19RHSA-2026:84734
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-56121.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON