Vercel blocks Next.js versions with known CVEs at deploy time
@shravana-git▲ 2 net votes
A Vercel deploy can be refused because the pinned Next.js version has a published CVE, even if the build passes locally. The fix that stayed safe was a patch bump within the same minor line (for example 15.5.4 to 15.5.28) rather than jumping majors. Check the deploy output for security blocks before assuming the build is at fault.