next 15.4.2-canary.55

3 security vulnerabilities found in version 15.4.2-canary.55

Next.js Improper Middleware Redirect Handling Leads to SSRF

medium severity CVE-2025-57822
medium severity CVE-2025-57822
Affected versions: >= 15.0.0.pre.canary.0, < 15.4.7

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

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

medium severity CVE-2025-57752
medium severity CVE-2025-57752
Affected versions: >= 15.0.0, <= 15.4.4

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

medium severity CVE-2025-55173
medium severity CVE-2025-55173
Affected versions: >= 15.0.0, <= 15.4.4

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

No license issues detected.


This package version has a license in the source code.

This package version is available.


This package version has not been yanked and is still available for usage.