Skip to content

[Snyk] Security upgrade lodash from 4.17.23 to 4.18.1#262

Open
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-e7bcbb77fbb012af16af923e458e8ecf
Open

[Snyk] Security upgrade lodash from 4.17.23 to 4.18.1#262
graymalkin77 wants to merge 1 commit intomainfrom
snyk-fix-e7bcbb77fbb012af16af923e458e8ecf

Conversation

@graymalkin77
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Arbitrary Code Injection
SNYK-JS-LODASH-15869625
  716  

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Arbitrary Code Injection

@graymalkin77
Copy link
Copy Markdown
Author

Merge Risk: Medium

This minor version upgrade for lodash introduces security fixes that alter existing behavior, warranting a medium risk assessment.

Key Changes:

  • _.unset / _.omit: To fix a prototype pollution vulnerability, calls attempting to traverse forbidden paths (like constructor or prototype) will now return false and not delete the property. Previously, these calls might have returned true. Code that relies on the return value of these functions for flow control may be impacted.
  • _.template: To fix a code injection vulnerability, the function will now throw an "Invalid imports option" error if the imports keys contain forbidden characters. Previously, this might have been ignored.

Recommendation: While these are important security updates, the changes introduce stricter validation and modified return values. It is recommended to verify that your application's usage of _.unset, _.omit, and _.template is not affected by this stricter behavior.

Source: GitHub Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Copilot AI review requested due to automatic review settings April 3, 2026 23:08
@graymalkin77
Copy link
Copy Markdown
Author

graymalkin77 commented Apr 3, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This Snyk-generated PR upgrades lodash to address a reported high-severity vulnerability in the project’s npm dependency tree.

Changes:

  • Bump lodash dependency in package.json to ^4.18.1.
  • Update package-lock.json to lock lodash to 4.18.1 (including updated resolved tarball URL and integrity hash).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Updates the direct lodash dependency range to ^4.18.1.
package-lock.json Locks node_modules/lodash to 4.18.1 and updates the root package dependency entry accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants