Live › vulnerability › CVE-2026-18948
Feast, a Python feature store, deserializes user-defined functions stored in its registry using the dill library without safe checks. A remote attacker can store a malicious UDF and get arbitrary code execution on the feature server, and an authenticated user can do the same on the registry server.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 16:25 UTC, 0h before NVD. All times on this page are UTC.
Teams running a Feast feature server or registry that is on a version before 0.67.0. The sources say the feature server is exploitable unauthenticated in default configurations, so any reachable deployment should be treated as exposed. Teams that do not run Feast servers in production, or that have already moved to 0.67.0 or later, can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| feast | pypi | < 0.67.0 | 0.67.0 |
pip show feast and compare it with the affected range below.0.67.0.0.67.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in Feast. The system improperly deserializes user-defined functions (UDFs) stored in its registry, which are serialized using the 'dill' library. This allows a remote attacker to store a malicious UDF, leading to unauthenticated arbitrary code execution on the feature server in default configurations. An authenticated attacker can also achieve arbitrary code execution on the registry server by bypassing authorization checks during deserialization. This vulnerability can result in cross-tenant data access and lateral movement within the system.
This page as .md · .json · in your agent: get_signal("CVE-2026-18948")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.