ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-77524

KEDA is a Kubernetes-based Event Driven Autoscaling component.

Published Oct 14, 2026 · catalog updated Oct 15, 2026 · KEDA is a Kubernetes-based

Check if you run it

No confirmed exploitation is on record for CVE-2026-77524. EPSS is 0.64%. Act only if a listed version of KEDA is a Kubernetes-based is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (KEDA is a Kubernetes-based).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.64%
Remediation
Version ranges on file
Affected products
Go github.com/kedacore/keda · Go github.com/kedacore/keda/v2 · go github.com/kedacore/keda · go github.com/kedacore/keda/v2 · golang github.com

## Summary A namespace admin who creates a and a in their own namespace can make the KEDA operator send its own ServiceAccount token to a tenant-controlled URL. That token holds cluster-wide, so it reads every Secret in every namespace, plus and create/delete cluster-wide, update on any workload, update (rewrite or disable cluster admission), and update (hijack aggregated API routing). This is effectively privilege escalation from namespace admin to cluster admin in real environments: a cluster-wide Secret read alone is enough to find a token for a more privileged ServiceAccount, and the cluster-wide create lets the attacker run a workload in any namespace whose Pod Security Admission level permits it (or that is PSA-exempt, such as , ) to reach the node filesystem and a control-plane kubeconfig. This is an incomplete fix of CVE-2025-68476: its content filter only requires the loaded file to be a JWT whose subject begins with , which the operator's own projected token satisfies by construction. The destination field is unvalidated. Finder credits: Artem Cherezov @cherez0ff, with Claude Opus 4.8 ## Verified live kind v1.31.2, kedacore/keda v2.20.0 (latest at the time of audit, ) installed from the unmodified release manifest ( ), default settings. ## Preconditions 1. The tenant holds on and in its own namespace (the documented KEDA tenant workflow), plus the built-in ClusterRole in that namespace. Often granted by a namespaced admin Role ( ) in multi-tenant environments. 2. KEDA is installed with default settings. ## Reproduction ### Cluster preparation (not part of the attack) ### Attack 1. Deploy a listener in the tenant namespace that impersonates a HashiCorp Vault server. It logs the login request body and replies with a well-formed Vault auth envelope. The KEDA operator uses the Vault Go client, which issues the login as an HTTP , so the listener must accept all methods. 2. Create the (the primitive) and a with a trigger referencing it. With and no block, KEDA d

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/kedacore/kedaversion unspecified
  • Go github.com/kedacore/keda/v20 → 2.21.0
  • go github.com/kedacore/keda<= 1.5.0
  • go github.com/kedacore/keda/v2< 2.21.0
  • golang github.comversion unspecified

How to fix CVE-2026-77524

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-77524. EPSS is 0.64%. Act only if a listed version of KEDA is a Kubernetes-based is installed.

Which versions are affected?

Compare what you have installed with 0 → 2.21.0, <= 1.5.0, < 2.21.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-269: Improper Privilege Management; CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.64%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Kubernetes security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · NIST NVD

    Detected

    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 tha

  2. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    github.com/kedacore/keda/v2 fixed in 2.21.0

  3. Oct 15, 2026 · GitHub Advisory Database

    Fix available

    github.com/kedacore/keda/v2 fixed in 2.21.0

  4. Oct 15, 2026 · GitHub Advisory Database

    Updated

    ## Summary A namespace admin who creates a and a in their own namespace can make the KEDA operator send its own ServiceAccount token to a tenant-controlled URL. That token holds cluster-wide, so it reads every Secret in every namespace, plus and create/delete cluster-wide, update on any workload, update (rewrite or disable cluster admission), and update (hijack aggregated API routing). This is eff

Sources

  • CVE.orgVulnerability recordCVE-2026-77524

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-77524

    30-day exploitation probability 0.6%

    first.org
  • GitHub Advisory DatabasePackage advisoryGHSA-637c-6jxx-4rwm

    KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-77524

    A namespace admin who creates a TriggerAuthentication and a ScaledObject in their own namespace can make the KEDA operator send its own ServiceAccount token to a tenant-controlled URL. That token holds [" "]/[" "] get cluster-wide, so it reads every Secret in every namespace, plus batch/jobs and horizontalpodautoscalers create/delete cluster-wide, */scale update on any workload, validatingwebhookc

    advisories.gitlab.com
  • NIST NVDVulnerability recordCVE-2026-77524

    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 authenticat

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-637c-6jxx-4rwm

    KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthentication

    osv.dev

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.