Skip to content

build(deps): bump next from 16.1.6 to 16.1.7#16

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-16.1.7
Open

build(deps): bump next from 16.1.6 to 16.1.7#16
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next-16.1.7

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 17, 2026

Bumps next from 16.1.6 to 16.1.7.

Release notes

Sourced from next's releases.

v16.1.7

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [Cache Components] Prevent streaming fetch calls from hanging in dev (#89194)
  • Apply server actions transform to node_modules in route handlers (#89380)
  • ensure maxPostponedStateSize is always respected (See: CVE-2026-27979)
  • feat(next/image): add lru disk cache and images.maximumDiskCacheSize (See: CVE-2026-27980)
  • Allow blocking cross-site dev-only websocket connections from privacy-sensitive origins (See: CVE-2026-27977)
  • Disallow Server Action submissions from privacy-sensitive contexts by default (See: CVE-2026-27978)
  • fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)

Credits

Huge thanks to @​unstubbable, @​styfle, @​eps1lon, and @​ztanner for helping!

Commits
  • bdf3e35 v16.1.7
  • dc98c04 [backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...
  • 9023c0a [backport] Disallow Server Action submissions from privacy-sensitive contexts...
  • 36a97b9 Allow blocking cross-site dev-only websocket connections from privacy-sensiti...
  • 93c3993 [backport]: feat(next/image): add lru disk cache and `images.maximumDiskCache...
  • c68d62d Backport documentation fixes for 16.1.x (#90655)
  • 5214ac1 [backport]: ensure maxPostponedStateSize is always respected (#90060) (#90471)
  • c95e357 Backport/docs fixes 16.1.x (#90125)
  • cba6144 [backport] Apply server actions transform to node_modules in route handlers...
  • 3db9063 [backport] [Cache Components] Prevent streaming fetch calls from hanging in d...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Greptile Summary

This PR is a security-focused Dependabot bump of next from 16.1.6 to 16.1.7, patching five CVEs in the Next.js framework. The corresponding lockfile is updated with the new @next/* package hashes and a set of transitive dependency upgrades that were pulled in by the resolver.

Key changes:

  • next bumped to 16.1.7 in apps/app/package.json, addressing:
    • CVE-2026-27979maxPostponedStateSize not always respected
    • CVE-2026-27980next/image LRU disk cache correctness
    • CVE-2026-27977 — Cross-site dev-only WebSocket connections from privacy-sensitive origins
    • CVE-2026-27978 — Server Action submissions from privacy-sensitive contexts
    • CVE-2026-29057 — HTTP request smuggling via http-proxy in rewrites
  • All @next/swc-* platform binaries updated to 16.1.7 in pnpm-lock.yaml
  • Transitive dependency version changes: graphql (16.12.0 → 16.13.1), caniuse-lite, postcss (8.5.6 → 8.5.8), tough-cookie (6.0.0 → 6.0.1), tldts/tldts-core, type-fest, @img/colour, @emnapi/runtime, baseline-browser-mapping, semver, @babel/runtime
  • vitest now resolves against jsdom@26.1.0 (down from jsdom@28.1.0); the older jsdom@28.1.0 package entry (which required node ^20.19.0 || ^22.12.0 || >=24.0.0) was removed entirely from the lock file, suggesting a dependency that required it was also removed or relaxed

Confidence Score: 5/5

  • This PR is safe to merge — it is a security patch release addressing five CVEs with no application code changes.
  • The only application-level change is the next version pin in package.json; the rest is a mechanically generated lockfile update. The release is a backport-only patch (16.1.6 → 16.1.7) with no new features, and Dependabot's compatibility score mechanism validates it against the existing test suite. All transitive dependency changes are minor patch-level bumps with no known regressions.
  • No files require special attention.

Important Files Changed

Filename Overview
apps/app/package.json Bumps next from 16.1.6 to 16.1.7; a straightforward single-line version change addressing multiple CVEs.
pnpm-lock.yaml Lock file updated to reflect next@16.1.7 and several transitive dependency version bumps (graphql, caniuse-lite, postcss, jsdom, tough-cookie, tldts, etc.); notably vitest now resolves against jsdom@26.1.0 instead of jsdom@28.1.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Dependabot PR: next 16.1.6 → 16.1.7] --> B[apps/app/package.json]
    A --> C[pnpm-lock.yaml]
    B --> D["next: 16.1.7 (pinned)"]
    C --> E["@next/env + @next/swc-* binaries → 16.1.7"]
    C --> F["Transitive deps updated\n(graphql, caniuse-lite, postcss, tough-cookie, tldts, etc.)"]
    C --> G["jsdom: 28.1.0 removed\nvitest resolves jsdom@26.1.0"]
    D --> H[Security patches applied]
    H --> I["CVE-2026-27977: WebSocket origin blocking"]
    H --> J["CVE-2026-27978: Server Action privacy context"]
    H --> K["CVE-2026-27979: maxPostponedStateSize fix"]
    H --> L["CVE-2026-27980: next/image disk cache"]
    H --> M["CVE-2026-29057: http-proxy smuggling fix"]
Loading

Last reviewed commit: "build(deps): bump ne..."

Bumps [next](https://github.com/vercel/next.js) from 16.1.6 to 16.1.7.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v16.1.6...v16.1.7)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 16.1.7
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 17, 2026
@vercel
Copy link

vercel bot commented Mar 17, 2026

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

Project Deployment Actions Updated (UTC)
better-registry Ready Ready Preview, Comment Mar 17, 2026 10:42pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants