Skip to content

[Snyk] Security upgrade sequelize from 4.42.0 to 6.1.0#58

Open
arunsingh wants to merge 1 commit intomasterfrom
snyk-fix-55cb8ae01e156f075336ae937f96370c
Open

[Snyk] Security upgrade sequelize from 4.42.0 to 6.1.0#58
arunsingh wants to merge 1 commit intomasterfrom
snyk-fix-55cb8ae01e156f075336ae937f96370c

Conversation

@arunsingh
Copy link
Copy Markdown
Owner

@arunsingh arunsingh commented Jan 25, 2026

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):

  • user-service/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  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


Note

Dependency upgrade

  • Bumps sequelize from ^4.42.0 to ^6.1.0 in user-service/package.json to remediate a reported vulnerability.

Note: This is a major version jump and may require compatibility checks elsewhere in the service.

Written by Cursor Bugbot for commit a459263. This will update automatically on new commits. Configure here.

@vercel
Copy link
Copy Markdown

vercel bot commented Jan 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
playbox-ott-znm2 Error Error Jan 25, 2026 5:59am

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jan 25, 2026

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on February 15

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

"jsonwebtoken": "^8.3.0",
"pg": "^7.7.1",
"sequelize": "^4.42.0",
"sequelize": "^6.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sequelize v6 removes operatorsAliases configuration option

High Severity

Upgrading sequelize from v4 to v6 is a major version upgrade with breaking changes. The existing configuration in user-service/src/config/sequelizeConfig.js uses operatorsAliases: false, which was removed in Sequelize v6. This option was deprecated in v5 (as a no-op) and completely removed in v6. The application will fail to initialize properly or throw errors when trying to instantiate the Sequelize connection with this invalid option.

Fix in Cursor Fix in Web

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