Use of Hard-coded Credentials Affecting feast package, versions [0,]
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Use of Hard-coded Credentials vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-FEAST-19883930
- published17 Sept 2026
- disclosed16 Sept 2026
- creditGeorge Chen
Introduced: 16 Sep 2026
NewCVE-2026-92787 (opens in a new tab)How to fix?
A fix was pushed into the master branch but not yet published.
Overview
feast is a Python SDK for Feast
Affected versions of this package are vulnerable to Use of Hard-coded Credentials via unverified intra-server JWT handling in sdk/python/feast/permissions/auth/oidc_token_parser.py, sdk/python/feast/permissions/auth/kubernetes_token_parser.py, and sdk/python/feast/permissions/security_manager.py. An attacker can bypass RBAC and gain trusted internal identity by sending a token whose preferred_username or Kubernetes service-account claim matches Feast’s hardcoded intra-communication value, even though the token signature is never verified before that claim is accepted. This lets a remote caller reach the server as an internal user and perform unchecked read and write operations across entities, feature views, data sources, and permission policies on any Feast deployment that exposes the affected auth path.