BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

CVE-2026-77524

9.9 critical SSVC exploitation: poc Published
NVD · CVE.org

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.

Fix

Microsoft's update · Critical

  • Release Notes — azl3 keda 2.14.1-19 on Azure Linux 3.0 · build 2.14.1-23

From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-29.

Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.

Change history 3

  1. StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 01:39
  2. StatusReceived → Awaiting AnalysisNVD modified 2026-10-16 16:00
  3. First seenCVSS 9.9NVD modified 2026-10-14 17:19

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 3