Skip to content

[Snyk] Security upgrade next from 16.3.5 to 16.4.5 - #399

Open
lance wants to merge 1 commit into
mainfrom
snyk-fix-938b7e5a195bbc63b7686a33978c4fa4
Open

lance wants to merge 1 commit into
mainfrom
snyk-fix-938b7e5a195bbc63b7686a33978c4fa4

Conversation

@lance

@lance lance commented Nov 19, 2026

Copy link
Copy Markdown
Member

snyk-top-banner

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
medium severity Race Condition
SNYK-JS-NEXT-22606112
  515  
medium severity Race Condition
SNYK-JS-NEXT-22606114
  515  

Breaking Change Risk

Merge Risk: Medium

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:

🦉 Race Condition

@lance

lance commented Nov 19, 2026

Copy link
Copy Markdown
Member Author

Merge Risk: Medium

This minor version upgrade from 16.3.5 to 16.4.5 includes important security patches and introduces a new recommended programming model.

Key Changes:

  • Security Fixes (v16.4.5): This is a security release that patches multiple vulnerabilities, including one high-severity and several medium-severity issues related to caching. The fixes address potential cache leaks, cache poisoning, and cross-user data exposure. These corrections might alter caching behavior in applications, especially those with complex or custom caching strategies.
  • New Caching Model (v16.4): This version establishes "Cache Components" as the recommended model for all Next.js applications, and it is enabled by default in new projects. For existing applications, this feature is opt-in and is not enabled automatically upon upgrading.
  • General Improvements: The release also includes smaller production bundles, reduced memory usage in development, and an upgrade to React 19.3.

Risk Assessment:

The risk is assessed as MEDIUM because the security fixes in 16.4.5 correct fundamental caching behaviors. While critical for security, these changes could impact applications that inadvertently relied on the previous, flawed logic.

Recommendation:
After upgrading, thoroughly test your application's caching functionality, especially if you use unstable_cache or have complex data-fetching patterns, to ensure behavior is consistent with the new, more secure implementation.

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

@qodo-for-securesign

qodo-for-securesign Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

PR Summary by Qodo

Upgrade Next.js to 16.4.5 to address race conditions

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Raise the Next.js dependency to 16.4.5 to address two reported race-condition vulnerabilities.
• Refresh the lockfile with matching Next.js packages and updated optional Sharp dependencies.
Merge Risk 🟡 Medium

Blast radius 🟢 Low 💥 1 capability

  • 1 affected end-to-end capability after fault-specific containment; implementation boundaries do not widen its functional scope.
  • The changed dependency is consumed by the single Pages Router application that serves the search page and its UI components.
  • The inspected consumers are entry points and rendering mechanisms within this same bounded integration; no independent functional scope or separate downstream product was identified.
Sources

package.json[28-28]

		"next": "^16.4.5",
Behavioral complexity 🟡 Medium 🧩 Compatibility cases

  • Before: the application was built and run with Next.js 16.3.5, matching SWC packages, and sharp 0.35.4.
  • After: package.json requests Next.js ^16.4.5 and the lockfile selects Next.js 16.4.5 with matching SWC packages and sharp 0.35.5.
  • New correctness condition: the upgraded framework/compiler/native-image set must remain compatible with this Pages Router application, its standalone output configuration, server-side props, next/link usage, and next/image rendering.
  • This is a compatibility condition introduced by the version transition, not a newly implemented application algorithm or concurrency protocol.
Sources

package.json[28-28]

		"next": "^16.4.5",

src/pages/index.tsx[1-3]

import type { NextPage, GetServerSideProps } from "next";
import Head from "next/head";
import { useState } from "react";
Potential damage 🟡 Medium 🩹 Temporary loss

  • A build/startup or framework-rendering fault can make the Rekor Search UI temporarily unavailable.
  • The failure does not by itself imply corruption of Rekor data or persistent application state.
  • Recovery requires a successful deployment of a compatible dependency set, commonly by rolling back the package and lockfile or correcting the dependency and rebuilding.
  • If deployment is atomic, an unsuccessful build may leave the prior version serving; that deployment behavior was not established by the inspected repository.
  • Revert package.json and package-lock.json to the prior compatible versions and redeploy, or produce a corrected build.
  • No migration, first-write adoption, persistent state repair, or external compensation is required by the changed files.
Sources

package.json[28-28]

		"next": "^16.4.5",

src/pages/index.tsx[1-3]

import type { NextPage, GetServerSideProps } from "next";
import Head from "next/head";
import { useState } from "react";
Assessed commit b6bad2b
Diagram

graph TD
  APP["Rekor UI"] --> MAN["Package manifest"] --> LOCK["npm lockfile"] --> NEXT["Next.js 16.4.5"] --> SWC["SWC binaries"]
  NEXT --> ENV["Next environment"]
  NEXT --> SHARP["Sharp 0.35.5"] --> IMG["Image binaries"]
Loading
High-Level Assessment

Upgrading the direct Next.js dependency and regenerating its lockfile is the appropriate approach for the reported vulnerabilities. An override would leave the declared framework version misaligned with its resolved packages; reviewers should still verify the build against the new minor version.

Files changed (2) +163 / -163

Other (2) +163 / -163
package.jsonRaise the Next.js dependency range to ^16.4.5 +1/-1

Raise the Next.js dependency range to ^16.4.5

• Changes the declared minimum Next.js version from 16.3.4 to 16.4.5 to target the reported race-condition vulnerabilities. No application source code changes.

package.json

package-lock.jsonResolve Next.js 16.4.5 and matching optional packages +162/-162

Resolve Next.js 16.4.5 and matching optional packages

• Updates the resolved Next.js version from 16.3.5 to 16.4.5, including @next/env and platform-specific SWC packages. Also refreshes optional Sharp, libvips, platform binaries, and Sharp's nested semver dependency.

package-lock.json

@qodo-for-securesign

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Qodo Logo

@codecov

codecov Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.15%. Comparing base (9cecf70) to head (b6bad2b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #399   +/-   ##
=======================================
  Coverage   87.15%   87.15%           
=======================================
  Files          15       15           
  Lines        1752     1752           
  Branches       96       96           
=======================================
  Hits         1527     1527           
  Misses        224      224           
  Partials        1        1           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This branch has not been deployed

No deployments
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