# CVE-2026-92787: Feast through 0.66.0 Authentication Bypass via Unverified Token

> Attackers bypass authentication by presenting unverified JWT tokens, gaining full read and write access to all server entities and permissions.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-4rxv-8f9g-9h5w

## What is CVE-2026-92787?

CVE-2026-92787 is a critical authentication bypass vulnerability in feast-dev feast, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-92787?


## How do I fix CVE-2026-92787?

No fix has been published for CVE-2026-92787 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92787 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92787 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92787 and fix it if it is affected.

What it is: CVE-2026-92787 is a critical authentication bypass vulnerability in feast-dev feast, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92787 exists.

Affected product: feast-dev feast. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92787/ (Markdown: https://insights.sbomify.com/CVE-2026-92787/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92787
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92787
- OSV: https://osv.dev/vulnerability/CVE-2026-92787

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92787/
Summaries are generated and may contain mistakes; the official description above is the record.