[SPARK-58256][INFRA][TEST] Fix npm vulnerabilities in ui-test and dev#57426
Closed
LuciferYang wants to merge 1 commit into
Closed
[SPARK-58256][INFRA][TEST] Fix npm vulnerabilities in ui-test and dev#57426LuciferYang wants to merge 1 commit into
LuciferYang wants to merge 1 commit into
Conversation
### What changes were proposed in this pull request? This clears the eight high-severity `npm audit` advisories that Dependabot reported against the two npm projects in the repo, `dev` and `ui-test`. All are resolved in range by `npm audit fix`, so only the two `package-lock.json` files change; no `package.json` and no direct dependency is touched. Package version changes: - `dev`: `brace-expansion` 1.1.14 -> 1.1.16, `js-yaml` 4.2.0 -> 4.3.0, `fast-uri` 3.1.2 -> 3.1.4. - `ui-test`: `js-yaml` 4.2.0 -> 4.3.0, and the several transitive `brace-expansion` copies to their patched releases (5.0.6 -> 5.0.7, 2.1.1 -> 2.1.2, 1.1.15 -> 1.1.16). ### Why are the changes needed? `npm audit` reports these high-severity advisories: - `brace-expansion` GHSA-3jxr-9vmj-r5cp (CVE-2026-13149): DoS via exponential-time expansion of consecutive non-expanding `{}` groups. - `js-yaml` GHSA-52cp-r559-cp3m (CVE-2026-59869): YAML merge-key chains can force quadratic CPU consumption. - `fast-uri` GHSA-4c8g-83qw-93j6 (CVE-2026-13676) and GHSA-v2hh-gcrm-f6hx (CVE-2026-16221): host confusion via failed IDN canonicalization and via a literal backslash authority delimiter. These are dev/test-only dependencies, but it is worth keeping the audit clean. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? `npm audit` reports 0 vulnerabilities in both projects, and `npm ci` reproduces the lockfiles cleanly. The `ui-test` jest suite (22 tests) and `dev/lint-js` both pass. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8)
Contributor
Author
dongjoon-hyun
approved these changes
Jul 22, 2026
HyukjinKwon
approved these changes
Jul 22, 2026
uros-b
approved these changes
Jul 22, 2026
Member
|
Merge Summary:
Posted by |
Contributor
Author
|
Thank you @dongjoon-hyun @HyukjinKwon @uros-b |
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
4 participants
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.
What changes were proposed in this pull request?
This clears the eight high-severity
npm auditadvisories that Dependabot reported against the two npm projects in the repo,devandui-test. All are resolved in range bynpm audit fix, so only the twopackage-lock.jsonfiles change; nopackage.jsonand no direct dependency is touched.Package version changes:
dev:brace-expansion1.1.14 -> 1.1.16,js-yaml4.2.0 -> 4.3.0,fast-uri3.1.2 -> 3.1.4.ui-test:js-yaml4.2.0 -> 4.3.0, and the several transitivebrace-expansioncopies to their patched releases (5.0.6 -> 5.0.7, 2.1.1 -> 2.1.2, 1.1.15 -> 1.1.16).Why are the changes needed?
npm auditreports these high-severity advisories:brace-expansionGHSA-3jxr-9vmj-r5cp (CVE-2026-13149): DoS via exponential-time expansion of consecutive non-expanding{}groups.js-yamlGHSA-52cp-r559-cp3m (CVE-2026-59869): YAML merge-key chains can force quadratic CPU consumption.fast-uriGHSA-4c8g-83qw-93j6 (CVE-2026-13676) and GHSA-v2hh-gcrm-f6hx (CVE-2026-16221): host confusion via failed IDN canonicalization and via a literal backslash authority delimiter.These are dev/test-only dependencies, but it is worth keeping the audit clean.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
npm auditreports 0 vulnerabilities in both projects, andnpm cireproduces the lockfiles cleanly. Theui-testjest suite (22 tests) anddev/lint-jsboth pass.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8)