Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityopen-source-dependency-vulnerabilitywidely-deployed-product-advisory

Next.js Patches Two Critical RCE Flaws in Caching and SVG Processing

Vulnerability Disclosure · 4 sources · Updated 29d ago · First seen Oct 15, 2026

Next.js Patches Two Critical RCE Flaws in Caching and SVG Processing

Next.js released out-of-band updates 16.4.1 and 15.5.28 to fix two critical unauthenticated remote code execution vulnerabilities and a high-severity denial-of-service flaw. The RCE issues, each rated 9.5, affect App Router applications with Cache Components whose cached functions return multiple typed arrays, and the Image Optimization API when processing SVG images through sharp and librsvg on glibc-based Linux. The denial-of-service flaw, rated 8.2, lets crafted requests exhaust CPU resources in App Router applications with at least one Server Action. No public reports indicated exploitation of these three flaws as of October 15, although an exploit exists for an earlier next/og issue linked to the same underlying librsvg weakness.

Administrators should upgrade immediately to the appropriate patched Next.js release and verify that sharp is 0.35.5 or later, particularly on Next.js 15, where upgrading the framework alone can retain a vulnerable dependency. Updating sharp addresses only the image-processing flaw; no known workaround exists for the Cache Components or Server Actions issues. Teams should inventory applications using these features and verify deployed dependency versions directly: as of October 15, the caching and Server Actions flaws lacked CVE identifiers and entries in the advisory feed used by npm audit, limiting reliance on automated audit results.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

8 events · Aug 2026 – Oct 14, 2026
  1. Reported Oct 15, 20261mo ago

    Netlify reports limited platform impact and recommends upgrading

    Netlify reported limited impact because its platform does not execute the affected image-optimizer code path. It nevertheless recommended upgrading Next.js.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
  2. Reported Oct 15, 20261mo ago

    Working exploit published for the earlier next/og vulnerability

    A working exploit targeting one specific server configuration was published for September's next/og flaw. Researcher Rafael B. Dias linked that flaw to CVE-2026-96889.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
  3. Oct 14, 20261mo ago

    Next.js releases emergency fixes for two RCE flaws and a denial-of-service flaw

    Next.js released versions 16.4.1 and 15.5.28 and published advisories addressing critical code-execution flaws in Cache Components and SVG processing, plus a Server Actions denial-of-service flaw. Reporting cautioned that version 15.5.28 deployments could retain vulnerable sharp 0.34.x dependencies and should verify that sharp 0.35.5 or later is installed.

    Next.js Security Update for Upstream Vulnerabilities | Next.js
  4. Sep 27, 20262mo ago

    Sharp fixes the librsvg vulnerability

    Sharp released a fix for CVE-2026-96889. Sharp 0.35.5 includes patched librsvg 2.63.2 and provides remediation for the affected Next.js image-processing path.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
  5. Sep 23, 20262mo ago

    CVE-2026-96889 is publicly disclosed

    The librsvg memory vulnerability CVE-2026-96889 was publicly disclosed. Next.js accesses the affected library through sharp, exposing certain SVG-processing deployments to remote code execution on glibc-based Linux.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
  6. Sep 2026

    Upstream dependency delays postpone two Next.js security fixes

    Two fixes intended for the September Next.js security release were postponed because of upstream dependency delays. They were subsequently included in the October out-of-band update.

    Next.js Security Update for Upstream Vulnerabilities | Next.js
  7. Sep 2026

    Next.js fixes next/og flaw involving attacker-controlled SVG generation

    A Next.js security fix addressed a next/og vulnerability in which attacker-controlled text could alter generated SVG. The issue was subsequently linked to the underlying librsvg weakness tracked as CVE-2026-96889.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
  8. Aug 2026

    Next.js addresses AVIF image-processing code-execution vulnerability

    Next.js issued a security fix for a libheif vulnerability involving crafted AVIF images, preceding the later SVG-related code-execution issues.

    Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Next.Js
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.