KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential

Summary

KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3.

Timeline

1. Dec 22, 2025, 9:35 PM UTCCVE published
2. Dec 22, 2025, 9:55 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Dec 22, 2025, 9:56 PM UTCRecord last updated

Affected versions

• kedacore keda

  fixed in 2.17.3; From 2.18.0 · fixed in 2.18.3

• github.com/kedacore/kedaGo

  All versions

• github.com/kedacore/keda/v2Go

  fixed in 2.17.3; From 2.18.0 · fixed in 2.18.3

• github.com/kedacore/keda/v2Go

  From 2.18.0 · fixed in 2.18.3

• github.com/kedacore/keda/v2Go

  fixed in 2.17.3

References 2