[Snyk] Security upgrade bcrypt from 5.1.1 to 6.0.0

[iamdrewfortini]

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

Snyk changed the following file(s):

• apps/backend/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	210

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to bolster the security of the apps/backend service by updating a critical dependency. The primary goal is to mitigate a known vulnerability within the bcrypt package, ensuring the application leverages a more secure and up-to-date version for password hashing and related cryptographic operations.

Highlights

• Security Upgrade: The bcrypt dependency in apps/backend/package.json has been upgraded from version 5.1.1 to 6.0.0. This update addresses a medium-severity vulnerability (SNYK-JS-TAR-15038581) related to improper handling of Unicode encoding.
• Manual Intervention Required: Snyk reported that it failed to automatically update the pnpm-lock.yaml file, which will require manual resolution before merging this pull request.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​15.2.3
	eslint-config-next@​15.2.3
	@​types/​react-dom@​19.1.9
	npm-run-all@​4.1.5
	@​stackframe/​stack-shared@​2.8.39
	@​types/​react@​19.1.13
	@​tailwindcss/​postcss@​4.1.13
	@​types/​node@​20.19.17
	rimraf@​5.0.10
	postcss@​8.5.6
	tailwindcss@​4.1.13
	wait-on@​8.0.5
	react@​19.1.1
	@​eslint/​eslintrc@​3.3.0 ⏵ 3.3.1
	typescript@​5.9.2
	react-dom@​19.1.1
	prettier@​3.6.2
	eslint@​9.36.0
	@​stackframe/​stack@​2.8.39
	convex@​1.27.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Next.js is vulnerable to RCE in React flight protocol CVE: GHSA-9qr9-h5gf-34mp Next.js is vulnerable to RCE in React flight protocol (CRITICAL) Affected versions: >= 14.3.0-canary.77 < 15.0.5; >= 15.1.0-canary.0 < 15.1.9; >= 15.2.0-canary.0 < 15.2.6; >= 15.3.0-canary.0 < 15.3.6; >= 15.4.0-canary.0 < 15.4.8; >= 15.5.0-canary.0 < 15.5.7; >= 16.0.0-canary.0 < 16.0.7 Patched version: 15.2.6 From: examples/convex/package-lock.json → npm/next@15.2.3 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[gemini-code-assist]

Code Review

This pull request upgrades bcrypt to version 6.0.0 to resolve a security vulnerability. While the upgrade is necessary, it's a major version bump that introduces critical breaking changes. The primary change is that bcrypt's asynchronous functions now return Promises instead of using callbacks. This requires code modifications wherever these functions are used. Additionally, the pnpm-lock.yaml file needs to be manually updated by running pnpm install. I've left a critical comment on the package.json change detailing the necessary actions to ensure the application continues to function correctly after this upgrade.

[gemini-code-assist]

This is a major version upgrade for bcrypt which introduces breaking changes. It's critical to address these to prevent runtime failures.

• Promise-based API: The asynchronous functions (genSalt, hash, compare) now return Promises instead of accepting callbacks. All call sites for these functions must be updated. For example, callback-style code like bcrypt.hash(myPassword, salt, (err, hash) => { ... }) should be refactored to use async/await (const hash = await bcrypt.hash(myPassword, salt);) or .then().

• Update Lockfile: As noted in the PR description, pnpm-lock.yaml was not automatically updated. You must run pnpm install manually to update the lockfile. Without this, the old version of bcrypt might still be used, or it could lead to dependency conflicts.

Given the nature of bcrypt in authentication flows, failing to address these points could break user sign-up and sign-in.