Arbitrary File Read in Feast Feature Server /read-document Endpoint
CVE-2026-23536 is an unauthenticated arbitrary file read vulnerability in Feast Feature Server affecting versions up to and including 0.58.0. The issue resides in the /read-document endpoint, implemented in the feature server component, where attacker-controlled file_path input is insufficiently restricted before being checked for existence and opened for reading. Because the endpoint accepts a path supplied in an HTTP POST request and reads the referenced file if it exists, a remote attacker can bypass intended access boundaries and retrieve the contents of arbitrary local files accessible to the server process. This can expose operating system files, application configuration, and stored secrets.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a remote unauthenticated attacker to read arbitrary files from the underlying host with the privileges of the Feast Feature Server process. The resulting exposure can include sensitive system information, application configuration, service credentials, and other secrets that may enable follow-on compromise, privilege escalation through credential reuse, or broader access to connected infrastructure and data services.
If you can’t patch tonight, do this now.
Until a fixed version is deployed, restrict network access to the Feast Feature Server so the vulnerable endpoint is not reachable by untrusted users or external networks. Place the service behind authentication and authorization controls, disable or remove the document-reading functionality if operationally feasible, and run the server with the minimum filesystem privileges necessary to reduce the set of readable files. Monitoring for unexpected access to the endpoint and reviewing exposed secrets on affected hosts are also advisable.
Patch, then assume compromise.
Upgrade Feast Feature Server to a version newer than 0.58.0 that properly restricts file access in the /read-document endpoint. The vulnerable functionality should be corrected by enforcing strict allowlisting of readable files or directories, canonicalizing and validating paths before access, and preventing user-controlled input from referencing arbitrary filesystem locations. If the endpoint is not required, remove or disable it in exposed deployments.
No public exploits tracked yet. Mallory keeps watching.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.