Skip to main content

CVE-2026-77524: CWE-269: Improper Privilege Management in kedacore keda

0
Critical
VulnerabilityCVE-2026-77524cvecve-2026-77524cwe-269cwe-918
Published: 10/14/2026 (10/14/2026, 16:15:15 UTC)
Source: CVE Database V5
Vendor/Project: kedacore
Product: keda

Description

KEDA versions 2.20.2 and earlier contain an improper privilege management vulnerability that allows a namespace administrator to escalate privileges to cluster-wide operator permissions by exploiting the handling of Vault authentication tokens. This issue is fixed in version 2.21.0.

CVSS v3.1

Score 9.9critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected software

kedacore

keda

Affected versions
<2.21.0
GitHub Actionsmore threats →ai
kedacore/keda
pkg:github/kedacore/keda
Affected versions
<2.21.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/14/2026, 16:48:23 UTC

Technical Analysis

KEDA, a Kubernetes-based Event Driven Autoscaling component, in versions 2.20.2 and earlier, allows a namespace administrator who can create TriggerAuthentication and ScaledObject resources to set the hashiCorpVault.address to a tenant-controlled endpoint and select Kubernetes authentication without an explicit credential. KEDA uses the operator pod's projected ServiceAccount token as a Vault login credential, which the attacker can leverage due to the JWT-shape filter accepting the operator token. This leads to privilege escalation, granting the attacker cluster-wide permissions including broad Secret reads and workload or admission-related operations. The vulnerability is addressed in version 2.21.0.

Potential Impact

An attacker with namespace administrator privileges can escalate to cluster-wide operator permissions, gaining broad access to Secrets and control over workload or admission operations. This represents a critical security risk with high confidentiality, integrity, and availability impact.

Mitigation Recommendations

Upgrade KEDA to version 2.21.0 or later, where this vulnerability is fixed. No other mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-08-20T20:23:02.508Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6acfaf362cdf04f65694d3b4

Added to database: 10/14/2026, 16:35:02 UTC

Last enriched: 10/14/2026, 16:48:23 UTC

Last updated: 10/14/2026, 16:51:03 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses