Advisory record · GHSA-c4p6-qg4m-9jmr

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

CVSS 8.2 HighEPSS 0.0063 · 50th percentile

Published by the GitHub Advisory Database at 22 Dec 2025, 20:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/kedacore/keda/v2Go>=2.18.0, <2.18.3 || <2.17.32.18.3, 2.17.3
Identifiers
GHSA-c4p6-qg4m-9jmr · CVE-2025-68476 · GO-2025-4257
Weakness (CWE)
CWE-22 · CWE-863
Published
22 Dec 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

KEDA versions below 2.17.3, and versions from 2.18.0 up to but not including 2.18.3, are vulnerable when TriggerAuthentication is used to configure HashiCorp Vault authentication. An attacker who can create or modify a TriggerAuthentication resource can read arbitrary files from the KEDA pod's node and send their contents to a server they control. Upgrade to 2.17.3 or 2.18.3. Limit create and update permissions on TriggerAuthentication resources to trusted users.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 50th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.