CVE-2026-92787 | 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.
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.
- 🔗 github.com/feast-dev/feast/issues/6785
- 🔗 github.com/feast-dev/feast
- 🔗 github.com/feast-dev/feast/blob/v0.66.0/sdk/python/f…
- 🔗 github.com/feast-dev/feast/blob/f296d4b/sdk/python/f…
- 🔗 github.com/feast-dev/feast/blob/f296d4b/infra/charts…
- 🔗 www.vulncheck.com/advisories/feast-through-0.66.0-authentic…
```Code``` unterstützt. Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | 2026-09-04 | 2026-09-21 |
|---|---|---|
| ≥90 % | 0 | 488 |
| ≥50 % | 0 | 1471 |
| ≥10 % | 0 | 7 |
| <10 % | 300 | 0 |
CVE-2026-92787 | 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.
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 tru
Noch keine Analyse zu CVE-2026-92787
Sei der Erste: Einschätzung, Betroffenheit, Workaround oder PoC — mit Antworten im Thread.