[Snyk] Security upgrade next from 13.1.6 to 15.2.2

[snyk-io]

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
	Missing Origin Validation in WebSockets SNYK-JS-NEXT-10259370	401

---

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.

Summary by Sourcery

Upgrade Next.js to v15.2.2 to fix a security vulnerability in WebSockets origin validation

Bug Fixes:

• Fix low-severity Missing Origin Validation in WebSockets vulnerability (SNYK-JS-NEXT-10259370)

Enhancements:

• Bump Next.js from v13.1.6 to v15.2.2

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
agent-gpt	❌ Failed (Inspect)			May 30, 2025 2:14am
solana-ai-agent-gpt5	❌ Failed (Inspect)			May 30, 2025 2:14am

[restack-app]

No applications have been configured for previews targeting branch: main. To do so go to restack console and configure your applications for previews.

[sourcery-ai]

Reviewer's Guide

This PR automatically upgrades the Next.js dependency from 13.1.6 to 15.2.2 by updating package.json and regenerating package-lock.json, resolving a missing WebSocket origin validation vulnerability.

Sequence Diagram: Snyk Automated Vulnerability Fix Process

sequenceDiagram
    participant Snyk
    participant ProjectRepo as "Project Repository"

    Snyk->>ProjectRepo: Scans dependencies for vulnerabilities
    activate ProjectRepo
    Snyk->>ProjectRepo: Detects vulnerability (SNYK-JS-NEXT-10259370 in next@13.1.6)
    Snyk->>ProjectRepo: Creates Pull Request to upgrade next from 13.1.6 to 15.2.2
    activate ProjectRepo
    ProjectRepo-->>Snyk: Pull Request created
    deactivate ProjectRepo
    deactivate ProjectRepo

Loading

Flow Diagram: Next.js Dependency Upgrade and Vulnerability Resolution

graph LR
    subgraph "Next.js Dependency Update"
        OldVer["next@13.1.6<br/>Vulnerability: SNYK-JS-NEXT-10259370"] -- "PR upgrades to" --> NewVer["next@15.2.2<br/>Status: Fixed"]
    end

Loading

File-Level Changes

Change	Details	Files
Upgrade Next.js to v15.2.2	Bump next version from 13.1.6 to 15.2.2 in package.json Regenerate package-lock.json to reflect the updated Next.js dependency	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[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@​13.1.6 ⏵ 15.2.2	+1		-3
	postcss@​8.4.23 ⏵ 8.4.31	+1	+5	-4

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 for details)
Warn		next@15.2.2 has a Critical CVE. CVE: GHSA-f82v-jwr5-mffw Authorization Bypass in Next.js Middleware (CRITICAL) Affected versions: >= 15.0.0, < 15.2.3 Patched version: 15.2.3 From: package-lock.json → npm/next@15.2.2 ℹ 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.2. 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.
Warn		caniuse-lite@1.0.30001720 has a License Policy Violation. License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: package-lock.json → npm/autoprefixer@10.4.14 → npm/jest@29.5.0 → npm/next@15.2.2 → npm/caniuse-lite@1.0.30001720 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001720. 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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[snyk-io]

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

✅ security/snyk check is complete. No issues have been found. (View Details)