CVE-2026-18948
Feast registry-stored functions could execute code during deserialization
Red Hat · Feast in Red Hat OpenShift AI
First documented disclosure · Review checkpoint
Summary
A malicious stored user-defined function could execute on feature or registry servers.
Severity and exploitation evidence
Critical · 9.9/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation is not established by the reviewed originals. Public demonstrations and catalog absence do not establish exploitation status.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Feast deserialized registry UDFs with dill without a sufficient trust or authorization boundary.
Conditions required
Ability to store a malicious UDF in the registry. Default feature-server configurations lack authentication; registry-server exploitation can bypass authorization for an authenticated principal.
Potential impact
Code execution can expose other tenants' data or enable lateral movement; these are impacts, not verified exploitation events.
Affected versions and configurations
Feast feature-server deployments and registry-server deserialization paths. Red Hat lists OpenShift AI 2.25, 3.3 and 3.4 feature-server corrections, while multiple pipeline/runtime and workbench packages remain affected; upstream numeric bounds are unverified.
Fix and mitigation status
For rhoai/odh-feature-server-rhel9: OpenShift AI 2.25 tag 1786110051, 3.3 tag 1786110033, and 3.4 tag 1786107278 (also later tag 1787068065). These component-specific errata do not establish fixes for listed pipeline or workbench packages; an upstream Feast fixed version was not verified.
Practical next steps
Apply the issue-specific correction: For rhoai/odh-feature-server-rhel9: OpenShift AI 2.25 tag 1786110051, 3.3 tag 1786110033, and 3.4 tag 1786107278 (also later tag 1787068065). These component-specific errata do not establish fixes for listed pipeline or workbench packages; an upstream Feast fixed version was not verified. Configure auth.type: kubernetes and deny registry writes by default to reduce exposure.
Operating lesson
Treat serialized registry functions as executable code and restrict registry writes.
Evidence and limits
Earliest reviewed public evidence 2026-08-10; CVE publication 2026-08-10. CVSS 3.1 9.9 is attributed to redhat in the CNA record. Red Hat public_date is August 10. The feature-server fixes are dated August 11 and August 27; its package_state still lists pipeline and workbench variants affected. No deployment-wide fix claim is made.
Sources
- redhat CVE authority record
Primary source ·
- Red Hat original security data and component errata
Primary source ·