Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-92787 – Authentication Bypass / Full RBAC Bypass – Feast Feature Server ≤ 0.66.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92787 is a critical authentication bypass vulnerability in Feast, the open-source feature store, affecting Feast Feature Server versions through 0.66.0. The flaw allows an unauthenticated attacker to present a JWT with a hardcoded, publicly-known claim value and have the server treat it as a trusted internal service — completely bypassing signature verification and all role-based access control (RBAC) checks. The issue carries a critical severity rating and can result in full read/write access to a Feast deployment’s data and configuration.

Technical details

  • Root cause: Feast’s OIDC and Kubernetes token parsers decode incoming JWTs with signature verification disabled (verify_signature: False) before comparing the token’s preferred_username / service-account name against an internal "intra-communication" identity value.
  • If that comparison matches, the function responsible for permission checks (is_auth_necessary()) returns False and no Permission object is ever evaluated — every permission check is skipped for that request.
  • Trigger condition: the trusted identity value is a hardcoded constant (base64("intra-server-communication")) shipped in Feast’s official Helm chart, so most default installations use a predictable, publicly-known value that has not been overridden.
  • Attack vector: network-based, unauthenticated. An attacker crafts a JWT containing the known claim with an arbitrary/empty signature and sends it to any of Feast’s exposed interfaces (REST API, gRPC, or Arrow Flight server).
  • Impact: complete authentication and authorization bypass, granting unauthenticated read and write access to all entities, feature views, data sources, and permission policies across every project, as well as exposure of sensitive connection details such as file paths and query strings.

Affected software

  • Feast (PyPI package feast) versions 0 through 0.66.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — 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

Mitigation and recommended actions

  • Immediate: Upgrade to a Feast release that fixes the unverified-token trust logic once a patched version is published by the maintainers; monitor the Feast GitHub repository and release notes for the fix corresponding to GitHub Issue #6785.
  • If no patch is available: Override the default INTRA_COMMUNICATION_BASE64 (or equivalent Helm chart) value with a unique, non-public secret rather than the documented default; restrict network exposure of Feast’s REST API, gRPC, and Arrow Flight endpoints to trusted internal networks only; enforce proper JWT signature verification at a reverse proxy or gateway layer in front of Feast; audit access logs for unexpected use of the intra-communication identity claim.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge