Repository navigation
Accept two more bundled undici 6.29.0 CVEs temporarily - #266
Merged
Merged
Conversation
npm 11.21.1 and 12.2.1, the latest releases on both lines, still bundle undici 6.29.0 through node-gyp. Two new high-severity advisories, CVE-2026-87018 and CVE-2026-109383, are fixed in undici 6.29.1, so every development image scan now fails the release gate. Scope temporary exceptions to that exact package path and version, next to the existing CVE-2026-109869 entry, tracked in #250 with the existing review date.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since about 2026-10-26 every development image build fails its security scan, on pull requests and on master. The regular images still pass. Example: run 41831506316.
Cause
Two new high-severity issues were published for the networking library that npm ships inside its own package. Only development images include npm. A fixed version of the library exists, but no npm release includes it yet: the newest npm 11 and npm 12 releases both still ship the affected version.
Solution
Accept these two issues temporarily, only for the copy of the library that comes with npm, the same way the earlier issue in that library was accepted. They are reviewed on the existing date or once npm ships the fix. Every other scan rule stays as it is, and the full scan report stays unfiltered.
Details
.github/actions/grype/exceptions.yaml: ignore CVE-2026-87018 and CVE-2026-109383 forundici6.29.0at/usr/lib/node_modules/npm/node_modules/undici/package.jsononly (bundled throughnode-gyp; fixed in undici 6.29.1; upstream Bundled undici@6.29.0 is vulnerable to CVE-2026-109383 (fixed in 6.29.1) npm/cli#10163). The existing CVE-2026-109869 entry stays. Removal is tracked in Remove temporary npm bundled-dependency CVE exceptions after upstream fixes #250; review date unchanged (2026-11-05).latest) and 11.21.1 (next-11) are still the newest releases, published 2026-10-15; both tarballs containnode_modules/undici6.29.0, so updating npm does not help yet.Validation
PHP_DEV=1 make, arm64), scanned with Grype 0.120.0 using the CI gate settings (squashed scope,--only-fixed, high cutoff,GRYPE_SHOW_SUPPRESSED):