Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| kedacore | keda | < 2.21.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Azure Linux
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Azure Linux 3 | keda | No fix yet | — |
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | k8sgpt | 0.4.40-r3 | — |
| Wolfi rolling | keda-2.19 +6 | No fix yet | — |
| Wolfi rolling | kserve-agent +3 | 0.21.0-r7 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | github.com/kedacore/keda | <= 1.5.0 | — | GHSA-637c-6jxx-4rwm |
| Go | github.com/kedacore/keda | all versions | — | GO-2026-6776 |
| Go | github.com/kedacore/keda/v2 | < 2.21.0 | 2.21.0 | GHSA-637c-6jxx-4rwm |