Skip to content

fix: resolve lodash prototype pollution vulnerability (CVE-2025-13465) #220

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

Merged
kherembourg merged 1 commit into from
Feb 16, 2026
Merged

fix: resolve lodash prototype pollution vulnerability (CVE-2025-13465) #220

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
30 changes: 15 additions & 15 deletions test-projects/rn-purchasely-test/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.

3 changes: 3 additions & 0 deletions test-projects/rn-purchasely-test/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,5 +36,8 @@
},
"engines": {
"node": ">=18"
},
"overrides": {
"lodash": ">=4.17.23"
Copy link

@gemini-code-assist gemini-code-assist bot Feb 16, 2026

Choose a reason for hiding this comment

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

medium

Using >= for the lodash version in overrides could be risky. If a new major version of lodash (e.g., 5.0.0) is released, npm might install it, which could introduce breaking changes. It's safer to use a caret ^ to restrict updates to minor and patch versions within the current major version. This ensures you get security patches without accidentally pulling in breaking changes.

Suggested change
"lodash": ">=4.17.23"
"lodash": "^4.17.23"

}
}
Loading