Directory Traversal Affecting kserve package, versions <0.16.0-r7


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.51% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KSERVE-14567842
  • published24 Dec 2025
  • disclosed22 Dec 2025

Introduced: 22 Dec 2025

CVE-2025-68476  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Chainguard kserve to version 0.16.0-r7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kserve package and not the kserve package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.