You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bumping direct dependencies to lodash ^4.18.1 does not stop the orchestrator workspace from also
installing lodash 4.17.23 and 2.4.2 via transitive dependencies, leaving older lodash copies in the
dependency tree. This can undermine the intended CVE remediation and keeps multiple lodash versions
in the install.
ⓘ Recommendations generated based on similar findings in past PRs
Evidence
The orchestrator yarn.lock shows multiple lodash versions resolved (4.18.1, 4.17.23, and 2.4.2). It
also shows which transitive dependencies constrain lodash to older ranges (e.g., ~4.17.21, ~4.17.15,
~2.4.1), and the workspace root package.json currently has no lodash override in its existing
"resolutions" block.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
### Issue description
Directly bumping lodash in a few packages still allows older lodash versions to be installed due to transitive dependencies that require `~4.17.x` and `~2.4.x`.
### Issue Context
`workspaces/orchestrator/yarn.lock` currently resolves multiple lodash versions, meaning the workspace install is not fully consolidated onto the intended patched lodash version.
### Fix Focus Areas
- Add/adjust a workspace-level Yarn `resolutions` override to force lodash to a single patched version (or upgrade/replace the transitive dependencies that pin lodash to older ranges).
- Re-run the install/update step to ensure `yarn.lock` converges and verify only the desired lodash version remains.
- workspaces/orchestrator/package.json[52-60]
- workspaces/orchestrator/yarn.lock[27865-27884]
- workspaces/orchestrator/yarn.lock[14115-14134]
- workspaces/orchestrator/yarn.lock[8447-8461]
- workspaces/orchestrator/yarn.lock[26610-26619]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
ⓘ The new review experience is currently in Beta. Learn more
• Created new changeset file documenting the lodash CVE fix
• Marks patch version bump for four orchestrator packages
• References CVE-2026-4800 security vulnerability
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
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.
manual cherry-pick of PR #2773
fixes https://access.redhat.com/security/cve/cve-2025-69873
fixes https://access.redhat.com/security/cve/CVE-2026-4926
fixes: https://access.redhat.com/security/cve/CVE-2026-4800
Hey, I just made a Pull Request!
✔️ Checklist