Next.js version 15.4.2 represents a minor update following 15.4.1, focusing primarily on internal improvements and bug fixes rather than introducing significant new features for developers. The core dependencies remain largely consistent, ensuring a stable upgrade path. Examining the package.json diff, the most notable changes involve the "@next/swc" and "@next/font" packages, reflecting updates to Next.js's Rust-based compiler and font optimization tooling which deliver improved build times and runtime performance.
While the listed devDependencies appear similar across both versions, closer scrutiny of detailed changelogs (external to the supplied data) often reveals targeted fixes for specific edge cases or build configurations, enhancing the developer experience. The optionalDependencies section also highlights updates to platform-specific SWC builds (@next/swc-*), crucial for ensuring optimal performance across diverse operating systems and architectures. From a dependency management perspective, migrating from 15.4.1 to 15.4.2 should be seamless for most projects, provided standard npm update procedures are followed. Developers should always consult the official Next.js release notes for a comprehensive listing of all changes, potential breaking behaviors (although unlikely in minor version bumps), and recommended upgrade strategies. The update ensures the React framework remains current, performant, and reliable for building modern web applications.
All the vulnerabilities related to the version 15.4.2 of the package
Next.js Affected by Cache Key Confusion for Image Optimization API Routes
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.
All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
Next.js Content Injection Vulnerability for Image Optimization
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on images.domains or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.
More details at Vercel Changelog
Next.js Improper Middleware Redirect Handling Leads to SSRF
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.
All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.
More details at Vercel Changelog
