AI Science Tracker

KEDA TriggerAuthentication can disclose the operator token to a tenant-controlled Vault URL

KEDA · AI involvement attributed to Claude Opus 4.8

Finding and attribution

A namespace tenant who can create TriggerAuthentication and ScaledObject resources can configure an unvalidated tenant-controlled HashiCorp Vault address. During Kubernetes Vault authentication, the operator sends its own projected ServiceAccount token to that endpoint. The advisory says this token has cluster-wide permissions, including reading Secrets across namespaces and creating workloads or changing cluster-level configuration, enabling privilege escalation from namespace admin to cluster admin. The demonstrated setup used default KEDA settings.

Product: KEDA. AI system: Claude Opus 4.8. Team / organization: Anthropic.

CVE identifiers: CVE-2026-77524.

AI and human contribution (source account): The KEDA security advisory explicitly credits finder Artem Cherezov working with Claude Opus 4.8. The source records a live verification on an unmodified KEDA 2.20.0 deployment. It does not give an internal discovery date.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The maintainer advisory documents public disclosure but does not establish whether defenders knew of the issue or whether it was exploited before disclosure.

Remediation status: fix documented. KEDA 2.21.0 fixes the issue in commit 1e21cc7 by enforcing explicit service-account token audiences and projection controls. The vendor release notes identify the CVE and describe configurations affected; this does not establish downstream deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 23 Sep 2026. AI attribution dated 23 Sep 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.9. Documented technical effects: privilege escalation, data disclosure, data modification.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-77524: CVSS 3.1 · 9.9 (Critical) · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. KEDA GitHub Security Advisory · checked 16 Nov 2026.

CVE-2026-77524: privilege escalation, data disclosure, data modification.
Prerequisites / affected scope: An authenticated namespace tenant needs permission to create TriggerAuthentication and ScaledObject in its namespace and the stated namespace edit permissions; default KEDA settings. The operator sends its privileged ServiceAccount token to the tenant-controlled Vault address. The advisory describes cluster-wide Secret access and cluster-wide workload/admission/API configuration privileges..
Exploitation evidence: The maintainer advisory includes a live verification/reproduction; it does not report exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: KEDA 2.21.0 fixes the issue in commit 1e21cc7 by enforcing explicit service-account token audiences and projection controls. The vendor release notes identify the CVE and describe configurations affected; this does not establish downstream deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases