CVE-2026-77524
validatedZero produced an exploit or a check.GHSA-637c-6jxx-4rwm ↗EUVD-2026-101431 ↗
description
KEDA versions through 2.20.2 can expose the operator ServiceAccount token through HashiCorp Vault authentication configured in a TriggerAuthentication resource. A namespace administrator who can create TriggerAuthentication and ScaledObject resources can direct the authentication request to a controlled endpoint and obtain the operator's permissions. The issue requires KEDA's default operator configuration and the relevant namespaced KEDA creation permissions.
mitigation
Upgrade github.com/kedacore/keda/v2 to version 2.21.0 or later. Until upgraded, prevent untrusted namespace administrators from creating TriggerAuthentication and ScaledObject resources, particularly configurations using HashiCorp Vault Kubernetes authentication.
fixed in 2.21.0
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-14 16:15Zghsa: trigger signal, started the run
- 2026-10-14 16:15Zpublic poc, published 2026-09-23 10:09Z
- 2026-10-14 16:15Zcve.org record for CVE-2026-77524
this entry in the feed
GET /api/v1/feed/CVE-2026-77524
{ "etk_id": "ETK-2026-1586", "cve_id": "CVE-2026-77524", "display_id": "CVE-2026-77524", "ghsa_id": "GHSA-637c-6jxx-4rwm", "euvd_id": "EUVD-2026-101431", "status": "published", "anchor_state": "anchored", "title": "Service account token exposure in KEDA Vault authentication", "summary": "KEDA versions through 2.20.2 can expose the operator ServiceAccount token through HashiCorp Vault authentication configured in a TriggerAuthentication resource. A namespace administrator who can create TriggerAuthentication and ScaledObject resources can direct the authentication request to a controlled endpoint and obtain the operator's permissions. The issue requires KEDA's default operator configuration and the relevant namespaced KEDA creation permissions.", "mitigation": "Upgrade github.com/kedacore/keda/v2 to version 2.21.0 or later. Until upgraded, prevent untrusted namespace administrators from creating TriggerAuthentication and ScaledObject resources, particularly configurations using HashiCorp Vault Kubernetes authentication.", "vendor": "go", "product": "go:github.com/kedacore/keda", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 1.5.0" ], "ecosystem": "go", "fixed_versions": [], "package_name": "github.com/kedacore/keda", "purl": "pkg:golang/github.com/kedacore/keda" }, { "affected_notes": [], "affected_ranges": [ "< 2.21.0" ], "ecosystem": "go", "fixed_versions": [ "2.21.0" ], "package_name": "github.com/kedacore/keda/v2", "purl": "pkg:golang/github.com/kedacore/keda/v2" } ], "cwes": [ 269 ], "cvss_score": 9.9, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "epss_score": 0.0064, "epss_percentile": 0.4952, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 48.38762685, "t0_at": "2026-10-14T16:15:15.268000+00:00", "signals": { "check": { "at": "2026-10-15T22:16:13.556394+00:00", "days": 1.2506746341898147, "is_lower_bound": false, "measured_at": "2026-10-14T16:15:15.268000+00:00", "url": null }, "public_poc": { "at": "2026-09-23T10:09:24+00:00", "days": -21.254065601851853, "is_lower_bound": false, "measured_at": "2026-10-14T16:15:15.268000+00:00", "url": "https://github.com/kedacore/keda/security/advisories/GHSA-637c-6jxx-4rwm" }, "trigger_signal": { "at": "2026-10-14T16:15:15.268000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-14T16:15:15.268000+00:00", "url": "https://github.com/kedacore/keda/security/advisories/GHSA-637c-6jxx-4rwm" } } }
published 2026-10-14 16:51Z
last change 2026-10-21 12:26Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.