Algorithmic Complexity Affecting kubeflow-pipelines package, versions <2.17.2-r3
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-CHAINGUARDLATEST-KUBEFLOWPIPELINES-19641565
- published8 Sept 2026
- disclosed3 Sept 2026
Introduced: 3 Sep 2026
CVE-2026-71429 (opens in a new tab)How to fix?
Upgrade Chainguard kubeflow-pipelines to version 2.17.2-r3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kubeflow-pipelines package and not the kubeflow-pipelines package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. Prior to 3.5.0, the path filters pick, ignore, filter, and replace in src/core/filters/filter-base.js recompute the full path string from the nesting stack for every checkable token. Because the stack length equals the current nesting depth and a checkable token is emitted at every level, a depth D document costs O(D²) rather than O(D) to process. The issue is triggered by nesting depth rather than byte volume, including the documented pick({filter: 'data'}) traversal-until-match path, so an application that sends untrusted JSON through a string or RegExp filter can block the Node.js event loop and cause denial of service with a small deeply nested document. The streamArray, streamObject, and streamValues streamers are not affected because they use the constant-time asm.depth getter. This issue is fixed in version 3.5.0.