CVE-2026-92787

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-16. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 19, 2026

Advisory Details (6)

Auto-updated Sep 19, 2026
No patch confirmed yet.
generic

Hardcoded intra-server-communication trust value in OidcTokenParser/KubernetesTokenParser allows full unauthenticated RBAC bypass · Issue #6785 · feast-dev/feast · GitHub

https://github.com/feast-dev/feast/issues/6785
generic

Feast through 0.66.0 Authentication Bypass via Unverified Token | Advisories | VulnCheck

https://www.vulncheck.com/advisories/feast-through-0.66.0-authentication-bypass-via-unverified-token
generic

feast/sdk/python/feast/permissions/security_manager.py at v0.66.0 · feast-dev/feast · GitHub

https://github.com/feast-dev/feast/blob/v0.66.0/sdk/python/feast/permissions/security_manager.py#L248-L264
generic

feast/sdk/python/feast/permissions/auth/oidc_token_parser.py at f296d4ba14c5d512429219b2b7845673e0fe524d · feast-dev/feast · GitHub

https://github.com/feast-dev/feast/blob/f296d4b/sdk/python/feast/permissions/auth/oidc_token_parser.py#L152-L156
generic

feast/infra/charts/feast-feature-server/templates/deployment.yaml at f296d4ba14c5d512429219b2b7845673e0fe524d · feast-dev/feast · GitHub

https://github.com/feast-dev/feast/blob/f296d4b/infra/charts/feast-feature-server/templates/deployment.yaml#L46-L47
generic

GitHub - feast-dev/feast: The Open Source Feature Store for AI/ML · GitHub

https://github.com/feast-dev/feast

Vendor Advisories for CVE-2026-92787(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 02:15 UTCGHSA enrichment
  2. 2026-09-19 22:18 UTCGHSA enrichment
  3. 2026-09-19 18:20 UTCEG score recompute
  4. 2026-09-19 18:20 UTCGHSA enrichment
  5. 2026-09-19 14:22 UTCGHSA enrichment
  6. 2026-09-19 10:24 UTCGHSA enrichment
  7. 2026-09-19 06:26 UTCGHSA enrichment
  8. 2026-09-19 02:29 UTCEG score recompute
  9. 2026-09-19 02:29 UTCGHSA enrichment
  10. 2026-09-19 01:51 UTCEG score recompute
  11. 2026-09-19 01:51 UTCGHSA enrichment
  12. 2026-09-18 22:11 UTCEG score recompute
  13. 2026-09-18 22:11 UTCGHSA enrichment
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-18 18:13 UTCGHSA enrichment
  16. 2026-09-18 14:15 UTCGHSA enrichment
  17. 2026-09-18 10:08 UTCGHSA enrichment
  18. 2026-09-18 06:11 UTCGHSA enrichment
  19. 2026-09-18 02:13 UTCGHSA enrichment
  20. 2026-09-17 22:16 UTCEG score recompute
  21. 2026-09-17 22:16 UTCGHSA enrichment
  22. 2026-09-17 19:32 UTCEPSS rescore
  23. 2026-09-17 18:18 UTCGHSA enrichment
  24. 2026-09-17 13:15 UTCGHSA enrichment
  25. 2026-09-17 09:18 UTCGHSA enrichment
Show 6 more
  1. 2026-09-17 05:20 UTCGHSA enrichment
  2. 2026-09-17 01:22 UTCEG score recompute
  3. 2026-09-17 01:22 UTCGHSA enrichment
  4. 2026-09-16 21:24 UTCEG score recompute
  5. 2026-09-16 20:38 UTCEG score recompute
  6. 2026-09-16 20:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92787?
CVE-2026-92787 is a critical vulnerability published on September 16, 2026. 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…
When was CVE-2026-92787 disclosed?
CVE-2026-92787 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92787 actively exploited?
CVE-2026-92787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.6% of all scored CVEs.
What is the CVSS score of CVE-2026-92787?
CVE-2026-92787 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-92787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92787, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92787

Explore →

Is Your Infrastructure Affected by CVE-2026-92787?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs