Fix lodash CVE-2026-4800 by bumping to 4.17.23#547
Open
imenkov wants to merge 1 commit into
Open
Conversation
Upgrades the direct lodash dependency from ^4.17.21 to ~4.17.23 to remediate CVE-2026-4800. Pinned with ~ to stay on the 4.17.x patched line and avoid the 4.18 series (4.18.0 is published as DEPRECATED with the maintainer note "Bad release. Please use lodash@4.17.21 instead.") - package.json: lodash ^4.17.21 -> ~4.17.23 - package-lock.json: regenerated via `npm install`; sole lodash node 4.17.21 -> 4.17.23 All 3 transitive consumers (archiver-utils, mocha-multi-reporters, async via winston/prompt) continue to dedupe to the single hoisted lodash. No overrides required. Source-code audit covers 22 lodash functions in use; all are stable across 4.17.x and no `_.template` usage exists. No source changes. S360-Run-Id: 495d2f2c-025e-4d09-ad47-bf5a23bad72f S360-KPI: SFI-ES5.2 S360-Skill: dependabot:dependency-update-orchestrator S360-Arm: dedicated_skill S360-Action-Items: 928b7015-db58-41a3-94ea-ab73c7bb9f4d:17027a63-3844-47e7-858a-baccf93ba52e
imenkov
changed the title
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
1 participant
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
Remediates CVE-2026-4800 (high) in
lodash.Change
package.json:lodash^4.17.21→~4.17.23package-lock.json: regenerated; solelodashnode4.17.21→4.17.23Why
~(tilde) instead of^(caret)lodash@4.18.0is published as DEPRECATED on npm with the maintainer note "Bad release. Please use lodash@4.17.21 instead." Caret would allow that bad release. Tilde keeps us on the 4.17.x patched line.Why no source changes
Source audit covers all 22 lodash functions in use across the repo. All are stable across the 4.17.x line.
_.templateis not used (the function with the historic prototype-pollution surface)._.set/_.mergecall sites use only statically-constructed paths.Files changed
package.jsonpackage-lock.jsonValidation
npm cisucceedsnpm run buildsucceeds — built binary runsTFX_TRACE=1traces correctlynpm test— 206 passing / 0 failing / 0 pending in ~36sVerified against
docs/contributions.mdend-to-end.🛠️ s360-breeze-toolkit · SFI-ES5.2 · run
495d2f2c