<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: Next.js incident updates</title>
  <link>https://pwn.watch/t/nextjs</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Thu, 22 Oct 2026 16:00:43 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/t/nextjs/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[critical] Next.js out-of-band release fixes two unauthenticated RCEs (SVG image optimization CVE-2026-96889, use cache)</title>
    <link>https://pwn.watch/i/nextjs-october-2026-rce-security-release</link>
    <guid isPermaLink="true">https://pwn.watch/i/nextjs-october-2026-rce-security-release</guid>
    <pubDate>Thu, 22 Oct 2026 16:00:43 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;On Oct 14 2026 Vercel shipped Next.js 16.4.1 and 15.5.28 with two critical unauthenticated remote code execution fixes held back from the September release: CVE-2026-96889 / GHSA-2464-fhr4-w9xw, a use-after-free in librsvg (via sharp) reachable through the Image Optimization API when SVGs are processed on glibc-based Linux, and GHSA-673q-mjm6-r5xr, RCE in App Router apps with Cache Components when a `use cache` function returns multiple typed arrays. A high-severity Server Actions DoS (GHSA-p3m5-59mp-jv5r) is fixed too. GitHub added the SVG advisory to its global database on Oct 22. No known exploitation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; live · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; next 15.5.28, next 16.4.1, sharp 0.35.5 (librsvg 2.63.2)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2026-10-22: GitHub publishes GHSA-2464-fhr4-w9xw to the global Advisory Database (critical), so Dependabot and npm audit start flagging affected next versions. (&lt;a href=&quot;https://github.com/advisories/GHSA-2464-fhr4-w9xw&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2026-10-14: Vercel releases Next.js 16.4.1 and 15.5.28 as an out-of-band security update: two critical unauthenticated RCEs (SVG Image Optimization, `use cache` typed arrays) and a high-severity Server Actions DoS. No workaround for the `use cache` bug; upgrade even if you don't use those features. (&lt;a href=&quot;https://nextjs.org/blog/nextjs-security-update-october-14-2026&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2026-10-14: Netlify: the SVG flaw is also reachable through `next/og` ImageResponse; on Netlify the next/image path runs on its Image CDN, and impact there is a crashed function, not code execution. (&lt;a href=&quot;https://www.netlify.com/changelog/2026-10-14-nextjs-react-security-vulnerabilities/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2026-96889&lt;/p&gt;</description>
  </item>
  <item>
    <title>[high] Next.js / React Server Components May 2026 security release</title>
    <link>https://pwn.watch/i/nextjs-react-may-2026-security-release</link>
    <guid isPermaLink="true">https://pwn.watch/i/nextjs-react-may-2026-security-release</guid>
    <pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;Coordinated May 6–7 2026 security release for React Server Components (CVE-2026-23870 DoS) and multiple Next.js advisories spanning middleware/proxy bypass, XSS, SSRF, cache poisoning and DoS. Upgrade Next.js to 15.5.18 or 16.2.6; react-server-dom-* to 19.0.6 / 19.1.7 / 19.2.6. Next.js 13.x/14.x had no planned patches.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; Next.js 15.5.18, Next.js 16.2.6, react-server-dom-* 19.0.6 / 19.1.7 / 19.2.6&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2026-23870&lt;/p&gt;</description>
  </item>
  <item>
    <title>[high] React Server Components DoS CVE-2026-23869 (April Next.js advisory)</title>
    <link>https://pwn.watch/i/react-rsc-dos-cve-2026-23869-april</link>
    <guid isPermaLink="true">https://pwn.watch/i/react-rsc-dos-cve-2026-23869-april</guid>
    <pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;April 8 2026 Next.js advisory GHSA-q4gf-8mx6-v5v3 tracks upstream CVE-2026-23869: crafted requests to App Router Server Function endpoints can cause excessive CPU / DoS. Patched in Next.js 15.5.15 and 16.2.3.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; 15.5.15, 16.2.3&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2026-23869&lt;/p&gt;</description>
  </item>
  <item>
    <title>[critical] React2Shell: CVSS 10 unauthenticated RCE in React Server Components and Next.js</title>
    <link>https://pwn.watch/i/react2shell-react-server-components-cve-2025-55182</link>
    <guid isPermaLink="true">https://pwn.watch/i/react2shell-react-server-components-cve-2025-55182</guid>
    <pubDate>Fri, 12 Dec 2025 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;A flaw in how React Server Components deserialize Flight payloads let an unauthenticated request run code on the server. Next.js App Router apps were affected by default. China-nexus groups including Earth Lamia and Jackpot Panda exploited it within hours of disclosure. CVE-2025-66478 (the Next.js id) was rejected as a duplicate.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; React 19.0.1, React 19.1.2, React 19.2.1, Next.js: patched release lines per the React/Next.js advisory&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-12-12: Unit 42 updates its threat brief on ongoing exploitation (&lt;a href=&quot;https://unit42.paloaltonetworks.com/cve-2025-55182-react-and-cve-2025-66478-next/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-12-05: CISA adds CVE-2025-55182 to KEV&lt;/li&gt;&lt;li&gt;2025-12-03: React discloses a critical vulnerability in React Server Components and ships fixes (&lt;a href=&quot;https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2025-55182&lt;/p&gt;</description>
  </item>
  <item>
    <title>[critical] Next.js middleware authorization bypass via x-middleware-subrequest (CVE-2025-29927)</title>
    <link>https://pwn.watch/i/nextjs-middleware-auth-bypass-cve-2025-29927</link>
    <guid isPermaLink="true">https://pwn.watch/i/nextjs-middleware-auth-bypass-cve-2025-29927</guid>
    <pubDate>Sat, 22 Mar 2025 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;Sending a crafted x-middleware-subrequest header made self-hosted Next.js skip middleware entirely, bypassing auth checks done there. Apps hosted on Vercel were protected. Fixed in 12.3.5, 13.5.9, 14.2.25 and 15.2.3; otherwise strip the header at the edge.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; 12.3.5, 13.5.9, 14.2.25, 15.2.3&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-03-22: Vercel publishes a postmortem on the bypass and its disclosure handling (&lt;a href=&quot;https://vercel.com/blog/postmortem-on-next-js-middleware-bypass&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-03-21: Next.js publishes advisory GHSA-f82v-jwr5-mffw (&lt;a href=&quot;https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2025-29927&lt;/p&gt;</description>
  </item>
</channel>
</rss>
