Symlink Attack Affecting github.com/nvidia/nvidia-container-toolkit/internal/edits package, versions <1.17.8
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-GOLANG-GITHUBCOMNVIDIANVIDIACONTAINERTOOLKITINTERNALEDITS-11023363
- published28 Jul 2025
- disclosed17 Jul 2025
- creditLei Wang, Min Yao
Introduced: 17 Jul 2025
CVE-2025-23267 Â (opens in a new tab)How to fix?
Upgrade github.com/NVIDIA/nvidia-container-toolkit/internal/edits to version 1.17.8 or higher.
Overview
Affected versions of this package are vulnerable to Symlink Attack though incorrect handling of the OCI hook createContainer during container initialization when update-ldcache is used. An attacker can modify data or disrupt service by supplying a specially crafted container image that triggers link following.
Workaround
When using the NVIDIA Container Runtime in legacy mode, disable the hook by editing the /etc/nvidia-container-toolkit/config.toml file and setting the features.disable-cuda-compat-lib-hook flag to true.
[features]
disable-cuda-compat-lib-hook = true
When using the NVIDIA GPU Operator, disable the hook by adding disable-cuda-compat-lib-hook to the NVIDIA_CONTAINER_TOOLKIT_OPT_IN_FEATURES environment variable. This can be done by including the following arguments when installing or upgrading the GPU Operator with Helm:
--set
"toolkit.env[0].name=NVIDIA_CONTAINER_TOOLKIT_OPT_IN_FEATURES" \
--set
"toolkit.env[0].value=disable-cuda-compat-lib-hook"