Skip to content

CVE-2026-92787 — Feast through 0.66.0 fails to verify JWT token signatures before establishing user…

Key facts

CVE-2026-92787 is a Critical (9.8) vulnerability: Feast through 0.66.0 fails to verify JWT token signatures before establishing user…. This entry ships a detection-only PoC and a Docker test lab.

CVE CVE-2026-92787
Severity Critical (9.8)
Detection / prevention —
PoC poc.py
Source 2026/CVE-2026-92787/

Details

English | 한국어

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.

Vulnerability Details

Property Value
CVE ID CVE-2026-92787
Type XSS
CVSS Score 9.8

Proof of Concept

Download

# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-92787/poc.py

Usage

# Run PoC against target
python3 poc.py --target <TARGET_URL>

# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>

⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.

Test Lab

This repository includes a Docker-based test environment with both vulnerable and patched applications.

Quick Start

# Clone and navigate to CVE directory
cd CVE-2026-92787

# Start both applications
docker-compose up -d

# Run tests
./run-tests.sh    # Linux/Mac
./run-tests.ps1   # Windows PowerShell

Application Endpoints

Application URL Status
Vulnerable App http://localhost:8080 Shows vulnerability
Patched App http://localhost:8081 Demonstrates fix

Directory Structure

├── README.md           # English documentation
├── README_KO.md        # Korean documentation
├── poc.py              # PoC detection script
├── docker-compose.yml  # Container orchestration
├── run-tests.sh        # Linux/Mac test runner
├── run-tests.ps1       # Windows test runner
├── vulnerable-app/     # Vulnerable version
│   ├── app.py
│   ├── Dockerfile
│   └── requirements.txt
└── patched-app/        # Fixed version
    ├── app.py
    ├── Dockerfile
    └── requirements.txt

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

Generated by PoC Generator on 2026-09-17T18:36:23.069571518

Frequently asked questions

What is CVE-2026-92787?

CVE-2026-92787 is a Critical (9.8) vulnerability: Feast through 0.66.0 fails to verify JWT token signatures before establishing user…. This entry ships a detection-only PoC and a Docker test lab.

How do I detect CVE-2026-92787?

Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.

How do I block or mitigate CVE-2026-92787?

Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.


For authorized security testing and research only. See the full source and NVD record.