<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g" -->

---
title: Next.js Security Update for a Critical Upstream Issue
description: An out-of-band security update for Next.js addresses a critical remote code execution vulnerability affecting the Node.js ImageResponse implementation in...
canonical: https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Next.js Security Update for a Critical Upstream Issue | daily.dev
og:description: An out-of-band security update for Next.js addresses a critical remote code execution vulnerability affecting the Node.js ImageResponse implementation in...
og:url: https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g
og:image: https://api.daily.dev/og/posts/j76AKXV6g.png
og:image:alt: Next.js Security Update for a Critical Upstream Issue
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Next.js Security Update for a Critical Upstream Issue

**[Next.js](https://daily.dev/sources/next)** · 2 min read · 0 upvotes · 0 comments

## Summary

An out-of-band security update for Next.js addresses a critical remote code execution vulnerability affecting the Node.js ImageResponse implementation in next/og. Versions 16.2.0 through before 16.3.6 are affected due to improper SVG escaping in Satori, an upstream dependency. Applications using the Edge ImageResponse implementation are not affected. Fixes ship in v16.3.6 (Active LTS) and v15.5.26 (Maintenance LTS, hardening only, not affected by the RCE issue). Developers are urged to upgrade immediately via npm install next@16.3.6 or next@15.5.26.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://nextjs.org/blog/nextjs-security-update-september-22-2026>

## Questions this post answers

### Is Next.js affected by a remote code execution vulnerability and how do I fix it?

Yes, Next.js versions 16.2.0 up to but not including 16.3.6 are affected by a critical remote code execution vulnerability in the Node.js ImageResponse implementation within next/og, caused by improper SVG escaping in the upstream Satori dependency. Upgrade to next@16.3.6 for the 16.3 line, or next@15.5.26 for 15.5 which includes related hardening though it is not affected by the RCE issue itself.

_Teams tracking Next.js dependency risk can follow security patches like this through daily.dev._

### Does the Next.js ImageResponse RCE affect the Edge runtime?

No, applications using the Edge ImageResponse implementation are not affected by the remote code execution vulnerability disclosed for Next.js. Only the Node.js ImageResponse implementation in next/og is impacted, specifically in versions 16.2.0 through versions before 16.3.6, due to a flaw in the Satori dependency used to generate SVG output.

_Developers scoping which runtime is exposed to a vulnerability rely on daily.dev to stay ahead of Next.js security advisories._

## Similar posts on daily.dev

- [Next.js Security Update for Upstream Vulnerabilities](https://daily.dev/posts/next-js-security-update-for-upstream-vulnerabilities-pgjwbgncx) · Next.js · 2 upvotes · 0 comments
- [Next.js May 2026 security release](https://daily.dev/posts/next-js-may-2026-security-release-hmqrmcava) · Vercel · 131 upvotes · 3 comments
- [September 2026 Security Release](https://daily.dev/posts/september-2026-security-release-z46gampdn) · Next.js · 2 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#nextjs](https://daily.dev/tags/nextjs), [#vercel](https://daily.dev/tags/vercel)

[View this post on daily.dev](https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Next.js Security Update for a Critical Upstream Issue","url":"https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g"},"datePublished":"2026-09-22T17:25:22.355Z","dateModified":"2026-09-22T17:25:42.501Z","description":"An out-of-band security update for Next.js addresses a critical remote code execution vulnerability affecting the Node.js ImageResponse implementation in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f5d165714784142918e35758887480b8?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f5d165714784142918e35758887480b8?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Next.js","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Next.js","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a7460ee33d92486cb5afd0fca36a116d","url":"https://daily.dev/sources/next"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,nextjs,vercel","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Next.js","item":"https://daily.dev/sources/next"},{"@type":"ListItem","position":3,"name":"Next.js Security Update for a Critical Upstream Issue"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/next-js-security-update-for-a-critical-upstream-issue-j76akxv6g#faq","mainEntity":[{"@type":"Question","name":"Is Next.js affected by a remote code execution vulnerability and how do I fix it?","acceptedAnswer":{"@type":"Answer","text":"Yes, Next.js versions 16.2.0 up to but not including 16.3.6 are affected by a critical remote code execution vulnerability in the Node.js ImageResponse implementation within next/og, caused by improper SVG escaping in the upstream Satori dependency. Upgrade to next@16.3.6 for the 16.3 line, or next@15.5.26 for 15.5 which includes related hardening though it is not affected by the RCE issue itself. Teams tracking Next.js dependency risk can follow security patches like this through daily.dev."}},{"@type":"Question","name":"Does the Next.js ImageResponse RCE affect the Edge runtime?","acceptedAnswer":{"@type":"Answer","text":"No, applications using the Edge ImageResponse implementation are not affected by the remote code execution vulnerability disclosed for Next.js. Only the Node.js ImageResponse implementation in next/og is impacted, specifically in versions 16.2.0 through versions before 16.3.6, due to a flaw in the Satori dependency used to generate SVG output. Developers scoping which runtime is exposed to a vulnerability rely on daily.dev to stay ahead of Next.js security advisories."}}]}
```

