Skip to content
All tool news

Tool desk · Updated daily

Tool news·Netlify·

Netlify Issues Security Guidance Following Next.js and React Vulnerability Disclosures.

Netlify outlines mitigation steps after Next.js and React disclosed 12 security vulnerabilities affecting middleware, XSS, and DoS.

CW

Create With tool desk

1 source checked · 2 min read · 3 sections

ShareLinkedIn
Netlify Issues Security Guidance Following Next.js and React Vulnerability Disclosures

Twelve Vulnerabilities Disclosed in Next.js and React

The Next.js and React teams disclosed twelve security vulnerabilities on May 6, 2026, spanning middleware bypass, cross-site scripting, server-side request forgery, cache poisoning, and denial of service. One vulnerability affects React Server Components, while eleven target Next.js itself. Netlify responded May 8 with specific guidance for developers running Next.js on its platform, clarifying which CVEs affect hosted projects and which do not.

Netlify recommends upgrading Next.js to version 15.5.18 or 16.2.6 and redeploying. This update pulls in the patched React Server Components dependency automatically. For projects using Pages Router with internationalization and Next.js Middleware or Proxy, developers must also update the OpenNext Netlify Next.js adapter to version 5.15.11. Projects with auto-installed adapters only require a redeploy.

Platform-Level Mitigations Neutralize Several CVEs

Netlify's platform architecture eliminates exposure to four of the disclosed vulnerabilities. The Image Optimization denial of service, WebSocket server-side request forgery, React Server Components cache poisoning, and cache-poisoned redirect bypass do not affect projects deployed on Netlify.

The platform's build and runtime infrastructure handles image optimization differently than standard Next.js deployments, preventing the DoS vector. WebSocket routing on Netlify bypasses the vulnerable Next.js middleware layer, while caching behavior for Server Components follows a distinct pattern that sidesteps the poisoning attack described in the React advisory. The redirect bypass, which relies on manipulating Next.js cache headers, similarly fails against Netlify's edge routing.

Remaining Vulnerabilities Require Upstream Patches

Seven Next.js vulnerabilities and the React Server Components DoS remain relevant to Netlify-hosted projects. These include middleware and proxy bypass issues, multiple cross-site scripting vectors, and server-side request forgery paths that could allow attackers to access internal resources or inject malicious content.

The React advisory GHSA-rv78-f8rc-xrxh describes a denial of service condition in react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack affecting React 19.0.0 through 19.0.5, 19.1.0 through 19.1.6, and 19.2.0 through 19.2.5. Developers using these packages outside Next.js must upgrade to 19.0.6, 19.1.7, or 19.2.6 depending on their minor version.

No proof-of-concept exploits have been published. The Next.js team assigned severity ratings ranging from moderate to high, with the React DoS rated high. Earlier minor versions of Next.js 15.x and 16.x will not receive patches; affected projects must upgrade to a supported minor release.

Netlify's full security update breaks down each CVE with specific impact assessments and mitigation steps for its platform.

Sources

1 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Latest tool news

What else changed this week.

All tool news
VercelDigest

What Vercel Shipped in Late October

Vercel shipped quicker static deployments, four AI Gateway models, more free domain choices and new CLI controls in late October. The changes cover developers testing sites…

Vercel

Vercel Adds Submit_feedback to Its MCP

submitfeedback is a new Vercel MCP tool that lets agents and harnesses send bug reports, friction reports and feature requests directly to the Vercel team. Feedback can include…

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.