External risk intelligence

Feast Feature Server Arbitrary File Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-23537

The vulnerability exists in a feature server endpoint. While network reachable, feature servers are typically deployed as internal data infrastructure components within a backend data pipeline, making direct public internet exposure uncommon in standard architectural patterns, though possible if misconfigured or exposed as part of a larger analytics service.

Remote Code Execution

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the Feast Feature Server that allows unauthenticated attackers to write arbitrary files, potentially overwriting critical system configurations or startup scripts. Because this flaw requires no credentials and can be exploited remotely, it could lead to unauthorized system changes, denial of service, or remote code execution. The main concern is confirming relevance and exposure.

Unauthenticated attackers can write files to servers.
It allows system compromise and potential code execution.
Confirm if this technology is used and if it's exposed.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker with network access to the Feast Feature Server can exploit a vulnerability in the `/save-document` endpoint. This flaw allows arbitrary JSON file writes to the server's filesystem, bypassing intended restrictions to overwrite critical configuration files or startup scripts. Successful exploitation could lead to unauthorized system changes, denial of service, or remote code execution.

No authentication or privileges required.
Write arbitrary JSON to filesystem.
System compromise, DoS, or RCE.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker with network access to the Feast Feature Server could write arbitrary JSON files to the server's filesystem, potentially overwriting critical application configurations or startup scripts. This could lead to unauthorized system modifications, denial of service, or remote code execution.

System configuration files at risk.
Attacker writes arbitrary JSON files.
System compromise or denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Feast Feature Server's `/save-document` endpoint likely falls under the purview of platform or data engineering teams responsible for the Feast deployment. Their first practical move should be to inventory all instances of the Feast Feature Server, confirm network reachability and business criticality for each, identify the specific system owner, and then prioritize remediation based on these findings.

Platform/Data Engineering owns the issue.
Verify Feast server network exposure and criticality.
Plan remediation based on identified risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Feast Feature Server?

Feast Feature Server is a core component used in machine learning operations to serve feature data for real-time model inference. It acts as a bridge between your stored data and your production models, ensuring that the necessary data inputs are readily available for predictions. Because it handles data serving within a backend pipeline, it is typically managed by data engineering teams.

What does CVE-2026-23537 mean?

This CVE describes a weakness classified as CWE-862, which is a Missing Authorization vulnerability. It means the software does not properly check if a user is allowed to perform a specific action. In this case, the server fails to verify identity before allowing access to the /save-document endpoint, permitting an unauthorized party to write files to the system unexpectedly.

How does an attacker trigger this vulnerability?

An attacker triggers this flaw by sending a specifically crafted request to the /save-document endpoint on the server. Because the system lacks authorization checks, it will process the request without requiring valid credentials. Note that simply having the server running on a private, isolated network segment does not automatically trigger the bug; the attacker must have network-level reachability to the server to send the malicious request.

Is my Feast Feature Server at risk?

Per Halo Surface Signal, these servers are generally deployed as internal data infrastructure components rather than public-facing services. While direct internet exposure is uncommon and generally unintended for this type of system, you should determine if your deployment is reachable from outside your secure environment or if it has been misconfigured to allow unauthorized network traffic.

What should I do if I run Feast?

Your first step is to locate all active Feast Feature Server instances within your infrastructure. Once you have an inventory, coordinate with your data engineering team to verify the network accessibility of each instance. Evaluate which servers are critical to your operations and monitor them closely while preparing to implement the necessary security updates or configuration changes to close the vulnerable endpoint.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.