[Power-Maverick]

Snyk has created this PR to fix 2 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
	Dependency on Vulnerable Third-Party Component SNYK-JS-NEXT-21460650	761
	Deserialization of Untrusted Data SNYK-JS-NEXT-21460652	761

Breaking Change Risk

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:

🦉 Deserialization of Untrusted Data

[Power-Maverick]

This upgrade from next version 16.3.8 to 16.4.1 is a minor version update that includes significant new features, behavioral changes, and critical security fixes.

Key Changes in v16.4.0:

• Cache Components: A new programming model is now recommended for all applications. While adoption is opt-in for existing apps, it will be the default for new projects and for Next.js 17.
• React 19.3 Support: The Next.js update ships with React 19.3. This requires developers to verify that existing client-side components, hooks, and state management behave as expected.
• Partial Prefetching: The behavior of prefetch={true} has changed to be more efficient by only prefetching reusable parts of a route. This is a behavioral change that could affect applications with specific dependencies on the previous prefetching mechanism.

Security Fixes in v16.4.1:

• This patch release is a crucial security update that addresses multiple vulnerabilities, including critical Remote Code Execution (RCE) and high-severity Denial of Service (DoS) issues.

Recommendation: The risk is assessed as medium not because of immediate breaking API changes, but due to the combination of a new recommended programming model, a behavioral change in prefetching, and the update to React 19.3. A thorough testing cycle is recommended to ensure application behavior remains correct, especially for client-side interactivity and navigation. Given the critical security fixes in v16.4.1, the upgrade is highly recommended.

Source: Next.js 16.4 Release Notes

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

[vercel]

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

Project	Deployment	Actions	Updated
web	Ready	Preview	Oct 23, 2026 4:10pm UTC

[Power-Maverick]

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

• SNYK-JS-NEXT-21460650
• SNYK-JS-NEXT-21460652

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.

---

This action was performed automatically by Snyk.