Skip to content

Pin dependency deepmerge to 4.3.1 [SECURITY] (2.x) #721

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: 2.x
Choose a base branch
from
+2 −2
Open

Pin dependency deepmerge to 4.3.1 [SECURITY] (2.x) #721

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/playground/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"@mapbox/mapbox-gl-geocoder": "^5.1.0",

@github-actions github-actions Bot Oct 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Pinning retains the vulnerable deepmerge release

4.3.1 is the vulnerable version identified by the cited CVE and advisory, so changing the range to an exact pin does not remediate prototype poisoning. Pin deepmerge to the first release that contains the security fix instead.

Confidence: high.

Reviewed by @weareikko/code-review v0.11.0 for commit 84b7ecd.

@github-actions github-actions Bot Nov 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: Pinning retains the vulnerable deepmerge version

The referenced advisory explicitly says deepmerge versions through 4.3.1 are vulnerable, so changing ^4.3.1 to 4.3.1 does not remediate the prototype-poisoning issue and prevents installation of a later fixed release. Pin a version newer than the vulnerable range instead.

Confidence: high.

Reviewed by @weareikko/code-review v0.11.1 for commit 82b5729.

"@motionone/easing": "^10.18.0",
"@studiometa/js-toolkit": "4.0.0-alpha.1",
"deepmerge": "^4.3.1",
"deepmerge": "4.3.1",
"gsap": "^3.13.0",
"mapbox-gl": "^3.13.0",
"morphdom": "^2.7.8",
Expand Down
Loading