Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77524 critical CVSS 9.9

Privilege Escalation in github.com/kedacore/keda (CVE-2026-77524)

Summary

Vulnerability in github.com/kedacore/keda (CVE-2026-77524). Successful exploitation can lead to full system takeover. Exploitable via PUT /v1/auth/kubernetes/login. Mitigation: upgrade to 2.21.0 or later.

Original description

The description as published by the source.

Summary

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, validatingwebhookconfigurations update (rewrite or disable cluster admission), and apiservices 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 batch/jobs create lets the attacker run a workload in any namespace whose Pod Security Admission level permits it (or that is PSA-exempt, such as kube-system , kyverno) 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 system:serviceaccount:, which the operator's own projected token satisfies by construction. The destination field hashiCorpVault.address 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 `keda-2.20.…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77524 has been found in github.com/kedacore/keda.
Attackers can target a specific entry point like PUT /v1/auth/kubernetes/login over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/kedacore/keda to 2.21.0 or later.
If unsure, ask your IT team or search "github.com/kedacore/keda CVE-2026-77524" on the vendor's site.

CVE-2026-77524 (github.com/kedacore/keda) — CWE-269 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /v1/auth/kubernetes/login / TriggerAuthentication / ScaledObject / horizontalpodautoscalers
Patched: 2.21.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in github.com/kedacore/keda. Attackers reach the vulnerable code path via PUT /v1/auth/kubernetes/login.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kedacore/keda. Attack surface: PUT /v1/auth/kubernetes/login / TriggerAuthentication / ScaledObject / horizontalpodautoscalers.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.21.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PUT /v1/auth/kubernetes/login requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/kedacore/keda' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/kedacore/keda' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/kedacore/keda を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PUT /v1/auth/kubernetes/login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PUT /v1/auth/kubernetes/login への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/kedacore/keda to 2.21.0

    ステージング環境で 2.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PUT /v1/auth/kubernetes/login on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/kedacore/keda
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/kedacore/keda/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.21.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details