WEBUI-2038: Fix json5 and tmp Dependabot vulnerabilities in lockfiles#3170
Merged
madhurkulshrestha-hyland merged 1 commit intoMay 21, 2026
Conversation
…CVE-2022-46175) The a11y package-lock.json was stale and still resolved babel-register -> babel-core -> json5@0.5.1 from the ftest package. Since babel-register was removed from ftest in the round 2 fix, regenerating the lockfile eliminates the vulnerable json5@0.5.1 dependency entirely. Fixes Dependabot alert #129.
|
04c5a7b
into
maintenance-3.1.x
13 of 14 checks passed
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.



Summary
Fixes two Dependabot alerts by updating stale lockfiles:
plugin/a11y/package-lock.jsonpackage-lock.jsonRoot Causes
json5@0.5.1 in a11y lockfile
The a11y
package-lock.jsonwas stale and still resolvedbabel-register→babel-core→json5@0.5.1from the ftest package. Sincebabel-registerwas removed from ftest in Round 2 (#3167), regenerating the lockfile eliminates the vulnerable dependency entirely.tmp@0.2.3 in root lockfile
The root
package-lock.jsonrecordedtmp@0.2.3for the ftest workspace sub-tree despite the override specifying^0.2.4. Updated the lockfile entry totmp@0.2.5which is what npm actually installs.Changes
plugin/a11y/package-lock.json(drops json5@0.5.1, babel-core, babel-register)packages/nuxeo-web-ui-ftest/node_modules/tmpentry in root lockfile from 0.2.3 → 0.2.5Verification