CVE-2025-68476: KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential
Impact 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.
Published Dec 22, 2025 · Updated Dec 23, 2025
Affected packages
github.com/kedacore/keda/v2
- Ecosystem
- Go
- Affected
- >= 2.18.0, < 2.18.3
- Fixed in
- 2.18.3
- Check
go list -m github.com/kedacore/keda/v2
github.com/kedacore/keda/v2
- Ecosystem
- Go
- Affected
- < 2.17.3
- Fixed in
- 2.17.3
- Check
go list -m github.com/kedacore/keda/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Patches
The problem has been patched in v2.17.3 and 2.18.3 as well as in main branch.
Workarounds
The only effective workaround is the strict restriction of permissions for creating and modifying TriggerAuthentication resources within the Kubernetes cluster.
Only trusted and authorized users should have create or update permissions on the TriggerAuthentication resource.
This limits an attacker's ability to configure a malicious TriggerAuthentication with an arbitrary path.
Is my project affected?
If it execute s
kubectl get deploy keda-operator -n keda -o jsonpath="{.spec.template.spec.containers[0].image}"and the version is not 2.17.3, 2.18.3 or >= 2.19.0, that version is affected.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
