CVE-2026-92787

Overview

Feast versions through 0.66.0 fail to properly verify JWT token signatures prior to authenticating user identity. This vulnerability allows an attacker to bypass role-based access control completely by presenting an unverified token containing a hardcoded claim. Successful exploitation grants full administrative read and write capabilities across the server's data sources, entities, and access policies.

Description

Feast through 0.66.0 fails to verify JWT token signatures before establishing user identity, allowing attackers to bypass all role-based access control by presenting an unverified token with a hardcoded claim value. Attackers can obtain trusted internal identity and gain unchecked read and write access to all entities, feature views, data sources, and permission policies on the server.

Impact

Impacts organization deployments using Feast feature store. Attackers can achieve complete loss of Confidentiality, Integrity, and Availability by gaining unchecked read and write access to all entities, feature views, data sources, and permission policies.

Remediation

Update Feast to a version past 0.66.0 where mandatory JWT signature verification is implemented. Ensure proper API gateway authentication and restrict network exposure of the Feast management interface to trusted hosts until patched.

Risk context

Assessed with Critical severity (CVSS v3 9.8 / CVSS v4 9.3) due to remote exploitability without requiring prior privileges or complex attack requirements. Immediate patching is recommended to prevent unauthorized administrative control.

Affected products

• Feast