Is CVE-2026-77524 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-77524 being exploited in the wild.

How severe is CVE-2026-77524?

Critical severity, with a CVSS score of 9.9, published 14 October 2026.

Which products and versions are affected?

github.com/kedacore/keda (Go) <= 1.5.0, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.0; github.com/kedacore/keda/v2 (Go) < 2.21.0, SEMVER:introduced=0,fixed=2.21.0; KEDA v2.20.0 and earlier.

How is CVE-2026-77524 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-77524?

Check whether you run github.com/kedacore/keda (Go), github.com/kedacore/keda/v2 (Go) or KEDA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-77524: KEDA privilege escalation from namespace admin to cluster admin via TriggerAuthentication

Q: Is there a fix for CVE-2026-77524?

Yes. github.com/kedacore/keda/v2 (Go): upgrade to 2.21.0 or later. Until then: Restrict the `create` and `get` permissions on `triggerauthentications.keda.sh` and `scaledobjects.keda.sh` resources to cluster administrators only, and disable HashiCorp Vault authentication in TriggerAuthentication if it is not required for your workloads. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-77524 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-77524?

Check whether you run github.com/kedacore/keda (Go), github.com/kedacore/keda/v2 (Go) or KEDA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-77524 · Severity: critical · CVSS 9.9 · Published 2026-10-14

KEDA is an autoscaler that uses custom resources to trigger workload scaling based on external metrics or events. A namespace administrator can craft a TriggerAuthentication resource pointing to a server they control, causing the KEDA operator to send its own cluster-admin token to that server. An attacker can then use this token to read secrets across all namespaces, create jobs in restricted namespaces like kube-system, and modify cluster-wide policies—effectively gaining full cluster administrative access.

Technologies: github.com/kedacore/keda (Go), github.com/kedacore/keda/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2026-77524 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-77524 being exploited in the wild.
How severe is CVE-2026-77524?: Critical severity, with a CVSS score of 9.9, published 14 October 2026.
Which products and versions are affected?: github.com/kedacore/keda (Go) <= 1.5.0, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.0; github.com/kedacore/keda/v2 (Go) < 2.21.0, SEMVER:introduced=0,fixed=2.21.0; KEDA v2.20.0 and earlier.
Is there a fix for CVE-2026-77524?: Yes. github.com/kedacore/keda/v2 (Go): upgrade to 2.21.0 or later. Until then: Restrict the `create` and `get` permissions on `triggerauthentications.keda.sh` and `scaledobjects.keda.sh` resources to cluster administrators only, and disable HashiCorp Vault authentication in TriggerAuthentication if it is not required for your workloads. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-77524 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-77524?: Check whether you run github.com/kedacore/keda (Go), github.com/kedacore/keda/v2 (Go) or KEDA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/kedacore/keda/v2 (Go): upgrade to 2.21.0 or later
```
go get github.com/kedacore/keda/v2@v2.21.0
```

Restrict the `create` and `get` permissions on `triggerauthentications.keda.sh` and `scaledobjects.keda.sh` resources to cluster administrators only, and disable HashiCorp Vault authentication in TriggerAuthentication if it is not required for your workloads.

Technical details

The vulnerability exists in KEDA's TriggerAuthentication handling for HashiCorp Vault integration. When a tenant creates a TriggerAuthentication with a tenant-controlled vault address and references it from a ScaledObject, the operator sends its own ServiceAccount token (projected at `/var/run/secrets/kubernetes.io/serviceaccount/token`) in the Vault login request. The prior mitigation (CVE-2025-68476) checks only that loaded content is a JWT with a subject starting with `system:serviceaccount:`, which the operator's own token satisfies by construction. The vault address field is entirely unvalidated, allowing tenant-controlled network endpoints. No user interaction is required; the attack triggers automatically during ScaledObject reconciliation.

Affected products

KEDA KEDA v2.20.0 and earlier

Identifiers

CVE-2026-77524
GHSA-637c-6jxx-4rwm
GO-2026-6776

Timeline

2026-10-15: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.