Unauthenticated RBAC bypass via unverified JWT identity
Published Sep 16, 2026 · Updated Sep 19, 2026
Authentication bypass in Feast 0 through 0.66.0 allows remote attackers to read and write server resources with a forged JWT. OidcTokenParser and KubernetesTokenParser decode the identity claim without signature verification and return the trusted intra-communication user before normal validation. A network-reachable server using OIDC or Kubernetes authentication with the chart's public default trust value accepts the forged identity and skips every RBAC permission check, exposing cross-project reads and writes.
Summary
What happened
Authentication bypass in Feast 0 through 0.66.0 allows remote attackers to read and write server resources with a forged JWT. OidcTokenParser and KubernetesTokenParser decode the identity claim without signature verification and return the trusted intra-communication user before normal validation. A network-reachable server using OIDC or Kubernetes authentication with the chart's public default trust value accepts the forged identity and skips every RBAC permission check, exposing cross-project reads and writes.
The record
- CVE
- CVE-2026-92787
- Published
- Sep 16, 2026
- Updated
- Sep 19, 2026
- Vendor
- Feast
- Product
- Feast
- Classifications
- CWE-798, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.66.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Feast issue 6785 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started