CVE-2025-68476: KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential

CVE-2025-68476 · Severity: medium · CVSS 4 · Published 2025-12-22

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.

Technologies: github.com/kedacore/keda (Go), github.com/kedacore/keda/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2025-68476 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-68476 being exploited in the wild.
How severe is CVE-2025-68476?
Medium severity, with a CVSS score of 4, published 22 December 2025.
Which products and versions are affected?
github.com/kedacore/keda (Go) SEMVER:introduced=0; github.com/kedacore/keda/v2 (Go) SEMVER:introduced=0,fixed=2.17.3,introduced=2.18.0,fixed=2.18.3, SEMVER:introduced=2.18.0,fixed=2.18.3.
Is there a fix for CVE-2025-68476?
Yes. github.com/kedacore/keda/v2 (Go): upgrade to 2.18.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-68476?
Check whether you run github.com/kedacore/keda (Go) or github.com/kedacore/keda/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/kedacore/keda/v2 (Go): upgrade to 2.18.3 or later
    go get github.com/kedacore/keda/v2@v2.18.3

Affected products

  • github.com/kedacore/keda (Go) SEMVER:introduced=0
  • github.com/kedacore/keda/v2 (Go) SEMVER:introduced=0,fixed=2.17.3,introduced=2.18.0,fixed=2.18.3, SEMVER:introduced=2.18.0,fixed=2.18.3

Identifiers

  • CVE-2025-68476
  • GHSA-c4p6-qg4m-9jmr
  • GO-2025-4257

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.