KEDA is a Kubernetes-based Event Driven Autoscaling component. In version 2.20.2 and earlier, a namespace administrator who can create TriggerAuthentication and ScaledObject resources can set hashiCorpVault.address to a tenant-controlled endpoint and select Kubernetes authentication without an explicit credential. KEDA then uses the operator pod's projected ServiceAccount token and sends it to that endpoint as a Vault login credential. The JWT-shape filter from the prior CVE-2025-68476 remediation accepts the operator token because its subject is a Kubernetes ServiceAccount, so the attacker can obtain the operator's cluster-wide permissions, including broad Secret reads and workload or admission-related operations. This vulnerability is fixed in 2.21.0.
CVE-2026-77524
“—” beside the score: it is equal to the CVSS score beside it.
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9CRITICALmedium confidence
- EG Risk
- 45EG Risk 45/100
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 (value × EchelonGraph’s weight)Severity99% × 45%The EG Score, 9.9 of 10.Exploitation0.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.6%
- EPSS %ILE
- 49th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 14, 2026
Last Modified
October 16, 2026
Advisory Details (3)
Auto-updated Oct 16, 2026Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication · Advisory · kedacore/keda · GitHub
https://github.com/kedacore/keda/security/advisories/GHSA-637c-6jxx-4rwmv2.21.0
Patch available: kedacore/keda v2.21.0
https://github.com/kedacore/keda/releases/tag/v2.21.0commit 1e21cc798ded (kedacore/keda)
Fix landed in kedacore/keda commit 1e21cc798ded — awaiting tagged release
https://github.com/kedacore/keda/commit/1e21cc798dedd079e696cdb45388eddc5e18365dVendor Advisories for CVE-2026-77524(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-77524Microsoft Security Response Center (MSRC)Critical
KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
- GHSA-637c-6jxx-4rwmGitHub Security AdvisoriesCritical
KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/kedacore/keda | — |
| — |
| github.com/kedacore/keda/v2 | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-16 00:18 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-14 17:29 UTCEG score recompute
- 2026-10-14 16:34 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
- 2026-10-14 16:29 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-77524?
When was the CVE record for CVE-2026-77524 published?
Is CVE-2026-77524 actively exploited?
What is the CVSS score of CVE-2026-77524?
How do I remediate CVE-2026-77524?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77524
Is Your Infrastructure Affected by CVE-2026-77524?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.