CVE-2025-68476: Github.com/kedacore/keda/v2 KEDA Has Arbitrary File Read Vulnerability

HIGH
Advisory Identifier: GHSA-c4p6-qg4m-9jmr
CWE-863 CWE-22
Published
Advisory Summary

CVE-2025-68476 is a HIGH keda has arbitrary file read vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/kedacore/keda/v2 libraries in the Go ecosystem. The issue involves keda has arbitrary file read via insufficient path validation in hashicorp vault service account credential. Remediation is available by upgrading affected packages to version 2.18.3, 2.17.3.

CVE-2025-68476 at a Glance

CVE Identifier CVE-2025-68476
GHSA Identifier GHSA-c4p6-qg4m-9jmr
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/kedacore/keda/v2
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-68476

To remediate this vulnerability, upgrade all affected Github.com/kedacore/keda/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/kedacore/keda/v2 fixed: 2.18.3
Upgrade github.com/kedacore/keda/v2 to 2.18.3
github.com/kedacore/keda/v2 fixed: 2.17.3
Upgrade github.com/kedacore/keda/v2 to 2.17.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/kedacore/keda/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-68476, inspect your project dependencies for Github.com/kedacore/keda/v2:

inspect dependencies for github.com/kedacore/keda/v2

Analyze the terminal output to locate any version of Github.com/kedacore/keda/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.18.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/kedacore/keda/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 ```bash 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.

CVE-2025-68476 Affected Github.com/kedacore/keda/v2 Versions

2 component(s)
Fixed Versions:
2.18.32.17.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kedacore/keda/v2
Go
≥ 2.18.0
< 2.18.3
2.18.3
github.com/kedacore/keda/v2
Go
< 2.17.3
2.17.3

References

Frequently Asked Questions

What is CVE-2025-68476?
CVE-2025-68476 is a security vulnerability in Github.com/kedacore/keda/v2 involving KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential under CWE-863: Incorrect Authorization.
Which Github.com/kedacore/keda/v2 versions are affected?
Affected versions include releases prior to 2.18.3, 2.17.3 across affected packages: github.com/kedacore/keda/v2.
What version fixes CVE-2025-68476?
Upgrading to 2.18.3, 2.17.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/kedacore/keda/v2 affected?
Yes, github.com/kedacore/keda/v2 is affected in releases prior to 2.18.3, 2.17.3. Upgrade your dependency to 2.18.3, 2.17.3 or later.
What CWE is associated with CVE-2025-68476?
CVE-2025-68476 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2025-68476?
Run the dependency tree command: 'inspect dependencies for github.com/kedacore/keda/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c4p6-qg4m-9jmr",
  "modified" : "2025-12-23T16:01:17Z",
  "published" : "2025-12-22T20:08:24Z",
  "aliases" : [ "CVE-2025-68476" ],
  "summary" : "KEDA has Arbitrary File Read via Insufficient Path Validation in HashiCorp Vault Service Account Credential",
  "details" : "### Impact\nAn Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication.\n\nThe vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount.\n\nAn 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.\n\nThe potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd.\n\n### Patches\nThe problem has been patched in v2.17.3 and 2.18.3 as well as in main branch.\n\n### Workarounds\nThe only effective workaround is the strict restriction of permissions for creating and modifying TriggerAuthentication resources within the Kubernetes cluster.\n\nOnly trusted and authorized users should have create or update permissions on the TriggerAuthentication resource.\n\nThis limits an attacker's ability to configure a malicious TriggerAuthentication with an arbitrary path.\n\n### Is my project affected?\nIf it execute s\n```bash\nkubectl get deploy keda-operator -n keda -o jsonpath=\"{.spec.template.spec.containers[0].image}\"\n```\nand the version is not 2.17.3, 2.18.3 or >= 2.19.0, that version is affected.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kedacore/keda/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.18.0"
      }, {
        "fixed" : "2.18.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kedacore/keda/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.17.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kedacore/keda/security/advisories/GHSA-c4p6-qg4m-9jmr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68476"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kedacore/keda/commit/15c5677f65f809b9b6b59a52f4cf793db0a510fd"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kedacore/keda"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-22T20:08:24Z",
    "nvd_published_at" : "2025-12-22T22:16:09Z"
  }
}