Next.js Content Injection Vulnerability for Image Optimization
Affected releases · next
- 15.x15.0.0 – 15.4.4Fixed in 15.4.5
- 14.x14.0.0 – 14.2.30Fixed in 14.2.31
- 13.x and older0.9.9 – 13.5.11No fix, no longer updated
On 15.x, the newest line:
npm install next@15.4.5Not affected
16.0.0 – 16.4.2
45 releases, latest
Affected
15.0.0 – 15.4.4
47 releases
Fixed
15.4.5 – 15.5.28
35 releases
Affected
14.0.0 – 14.2.30
41 releases
Fixed
14.2.31 – 14.2.35
5 releases
Affected
13.0.0 – 13.5.11
56 releases
Affected
12.0.0 – 12.3.7
33 releases
Affected
11.0.0 – 11.1.4
7 releases
Affected
10.0.0 – 10.2.3
18 releases
Affected
9.0.0 – 9.5.5
38 releases
Affected
8.0.0 – 8.1.0
6 releases
Affected
7.0.0 – 7.0.3
4 releases
Affected
6.0.0 – 6.1.2
7 releases
Affected
5.0.0 – 5.1.0
2 releases
Affected
4.0.0 – 4.2.3
15 releases
Affected
3.0.1 – 3.2.3
11 releases
Affected
2.0.0 – 2.4.9
17 releases
Affected
1.0.0 – 1.2.3
10 releases
Not affected
0.1.0 – 0.4.1
23 releases
Affected
0.9.9 – 0.9.11
3 releases
Is your project affected?
Paste your package.json, or type the range you declare for next. It is read in your browser and sent nowhere.
What happens
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