CVE-2026-92787

CVSS 9.8 (critical) · published 2026-09-16

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.

Weakness: CWE-798

Source: NVD CVE-2026-92787

References

• https://github.com/feast-dev/feast
• https://github.com/feast-dev/feast/blob/f296d4b/infra/charts/feast-feature-server/templates/deployment.yaml#L46-L47
• https://github.com/feast-dev/feast/blob/f296d4b/sdk/python/feast/permissions/auth/oidc_token_parser.py#L152-L156
• https://github.com/feast-dev/feast/blob/v0.66.0/sdk/python/feast/permissions/security_manager.py#L248-L264
• https://github.com/feast-dev/feast/issues/6785
• https://www.vulncheck.com/advisories/feast-through-0.66.0-authentication-bypass-via-unverified-token
• https://github.com/feast-dev/feast/issues/6785

Check your software

Connect an AI agent to the Fixlane MCP server or ask the Telegram bot to check what you have installed against incidents with a verified fixed version.