Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 4, published 30 September 2026.
- Which products and versions are affected?
- next (npm) SEMVER:introduced=16.2.0,fixed=16.3.6; Vercel Next.js 16.2.0 to 16.3.5.
- Is there a fix for This vulnerability?
- Yes. next (npm): upgrade to 16.3.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- next (npm): upgrade to 16.3.6 or later
npm install next@16.3.6
Technical details
An improper escaping flaw in the Satori SVG library (a dependency of next/og) permits crafted SVG attribute and content injection. When Next.js applications pass untrusted input from requests into ImageResponse SVG rendering on the Node.js runtime (not the Edge runtime), attackers can inject malicious SVG markup that is interpreted and executed. The vulnerability requires application code to pass attacker-controlled URL parameters or user input directly into SVG attributes, content, or styles without sanitization.
Affected products
- Vercel Next.js 16.2.0 to 16.3.5
Timeline
- 2026-09-22: disclosed
- 2026-09-22: patched: version 16.3.6