Skip to content

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

Open
codecademydev wants to merge 1 commit intomainfrom
snyk-fix-38d13779b9d07510b42bcf69a31c2bc7
Open

[Snyk] Security upgrade lodash from 4.17.23 to 4.18.1#3315
codecademydev wants to merge 1 commit intomainfrom
snyk-fix-38d13779b9d07510b42bcf69a31c2bc7

Conversation

@codecademydev
Copy link
Copy Markdown
Collaborator

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Arbitrary Code Injection
SNYK-JS-LODASH-15869625
  716  
medium severity Prototype Pollution
SNYK-JS-LODASH-15869619
  631  

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:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

@codecademydev codecademydev requested a review from a team as a code owner April 3, 2026 07:02
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 3, 2026

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 226206171a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"@vidstack/react": "^1.12.12",
"core-js": "3.7.0",
"lodash": "^4.17.23",
"lodash": "^4.18.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update lockfile when bumping lodash range

Changing lodash to ^4.18.1 without a corresponding yarn.lock update will break installs in this repo’s CI, because the shared setup action runs yarn install --immutable (.github/actions/yarn/action.yml:16) and immutable mode rejects manifest/lock drift. I checked yarn.lock and it still only contains the lodash@npm:^4.17.23 descriptor (no ^4.18.1 entry), so workflows that use this action will fail before tests/builds.

Useful? React with 👍 / 👎.

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.

2 participants