CVE-2026-92787

Feast through 0.66.0 Authentication Bypass via Unverified Token

Published Sep 16, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Feast 0.66.0 and earlier modules incorrectly accept JWT tokens without verifying their cryptographic signatures. The resulting authentication bypass allows an attacker to impersonate any user, granting complete visibility and write access to all managed entities, feature views, data sources, and permission policies. This flaw is a direct violation of role‑based access control and effectively lets an attacker take full control of the Feast server.

Affected Systems

Feast (feast-dev:feast) versions up to and including 0.66.0.

Risk and Exploitability

The nominal severity is high, with a CVSS score of 9.3, and the EPSS score of less than 1% suggests a currently low probability of exploitation. The flaw is not listed in the CISA KEV catalog, but the attack vector is inferred to be remote through the Feast API or any exposed authentication endpoint where an attacker can inject a forged token. The vulnerability’s weakness is described by CWE‑798, representing an improper verification of token signatures.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Feast to version 0.66.1 or later, which enforces proper JWT signature verification.
  • Validate that the deployment configuration enforces signature checks and removes any hardcoded claim overrides in the OID token parsing logic.
  • Monitor authentication logs for anomalous token usage and restrict network access to the Feast API to trusted hosts.

Generated by OpenCVE AI on September 18, 2026 at 05:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Feast-dev
Feast-dev feast
Vendors & Products Feast-dev
Feast-dev feast
Type Values Removed Values Added
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.
Title Feast through 0.66.0 Authentication Bypass via Unverified Token
Weaknesses CWE-798
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 19, 2026, 1:42 AM
Reserved
Sep 16, 2026, 7:31 PM
Status
Deferred
Published
Sep 16, 2026, 9:17 PM
Modified
Sep 24, 2026, 9:08 PM