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.
References7
- github.com/feast-dev/feast
- github.com/feast-dev/feast/blob/f296d4b/infra/charts/feast-feat…
- github.com/feast-dev/feast/blob/f296d4b/sdk/python/feast/permis…
- github.com/feast-dev/feast/blob/v0.66.0/sdk/python/feast/permis…
- github.com/feast-dev/feast/issues/6785
- www.vulncheck.com/advisories/feast-through-0.66.0-authenticatio…
- github.com/feast-dev/feast/issues/6785
Metrics
- CVSS 3.1
-
9.8
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 4.0
-
9.3
CRITICAL
Score source: CNA
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 1% percentile: 53 · as of 8 November 2026
- CWE
- CWE-798
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.