Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTTP request with malicious parameter
-
DeliveryValue passed into next/og Node.js ImageResponse SVG
-
ExploitImproper escaping injects SVG markup
-
ExecutionEscalation to code execution in Node.js runtime
-
ImpactRemote code execution on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding for downstream
|
| Exploitation Conditions | Exploitation requires that the application pass attacker-controlled values into SVG content, attributes, or styles during image generation - concretely, the Node.js ImageResponse implementation from next/og (Next.js >=16.2.0 <16.3.6) or direct use of Satori (0.0.27-0.33.4) to render untrusted input. Limiting factors: the Edge ImageResponse implementation is NOT affected; applications that never route attacker-controlled data into SVG are NOT affected (this AT:P deployment prerequisite, not authentication, is the main brake on exploitation); no login is needed once such a route exists (PR:N). The only complete remediation is upgrading (Satori 0.33.5 / Next.js 16.3.6); the interim mitigation is to stop rendering attacker-controlled content through the Node.js path. |
| Impact | This is a genuine priority for the affected population despite the modest 5.3 CVSS 4.0 base score, because that vendor score was computed against Satori-the-library in isolation (VC:N/VI:N/VA:N with subsequent-system SC:H/SI:H) whereas the real-world consumer, Next.js next/og, escalates the identical flaw to remote code execution per the Next.js GHSA-vcvr-r3jv-pc5j advisory. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:P) shows an unauthenticated, network-reachable issue whose only friction is a deployment prerequisite (AT:P): the application must feed attacker-controlled data into SVG content/attributes/styles. No EPSS score, KEV listing, or public weaponized exploit was provided, so there is no evidence of active exploitation yet; however the advisories include a concrete reproduction pattern that makes exploit development straightforward. Signals conflict: the numeric CVSS reads 'medium' but the vendor-described impact is RCE - the divergence is an artifact of scoping the score to the library rather than the consuming runtime, and defenders should treat next/og Node.js deployments as high-risk. Note the tag 'Information Disclosure' is inconsistent with the CWE-116 injection-to-RCE nature of this flaw. |
| Exploit ScenarioDerived | A Next.js application exposes an OG-image route that inserts a user-supplied query parameter into SVG (e.g. inside a <title> or attribute) via the Node.js next/og ImageResponse. An unauthenticated attacker sends a crafted request whose value breaks out of the intended text context and injects SVG markup, which - because Satori fails to escape it - is interpreted as active markup and, in the Node.js rendering path, escalates to remote code execution on the server. No public weaponized exploit was provided, but the vendor advisories include a working reproduction pattern. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Improper output escaping in Satori (an HTML/CSS-to-SVG rendering library) allows crafted values to be interpreted as SVG markup, and when those values are routed through the Node.js ImageResponse implementation from Next.js's next/og, the same flaw escalates to remote code execution. Affected are Satori versions 0.0.27 through 0.33.4 and Next.js versions 16.2.0 through 16.3.5 that pass attacker-controlled data into SVG content, attributes, or styles; the Edge ImageResponse path and applications that never feed untrusted values into SVG are not affected. Exploitation is unauthenticated per the CVSS vector (PR:N) but hinges on that deployment prerequisite, and no public exploit identified at time of analysis. Vendor-released patches exist in Satori 0.33.5 and Next.js 16.3.6.
RemediationAI
Upgrade Satori to 0.33.5 (or later) and Next.js to 16.3.6 (or later); these are the vendor-released patches and the only complete fix, since the flaw lives in the library's serialization internals and cannot be reliably neutralized by application-level input filtering. For teams that cannot upgrade immediately, the vendor workaround is to stop passing attacker-controlled values into SVG content, attributes, or styles handled by the Node.js ImageResponse implementation from next/og - this constrains the affected endpoint's functionality but is the recommended interim step, and Satori's own advisory notes that applications which cannot upgrade should not render attacker-controlled content with Satori at all. A partial alternative is to move affected image-generation routes to the Edge ImageResponse implementation, which is not affected, but this trades away Node.js runtime APIs and may break routes that depend on them. Because the CVSS 4.0 vector carries E:X (exploit maturity undefined) and no public exploit or KEV entry has been identified, treat this as a patch-urgently item rather than an emergency, prioritizing any route where request parameters, headers, or user content reach next/og. Reference advisories and fix commits: https://github.com/vercel/satori/security/advisories/GHSA-wx4j-mvgx-mqwp, https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j, https://github.com/vercel/satori/pull/814, https://github.com/vercel/satori/commit/26a52affc031216fee5882b6e965c8dbc7ac1782, and https://github.com/vercel/next.js/commit/868fad38690d72088868f299fa2bef339b26838e.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Satori converts HTML and CSS into SVG, and this CVE is rooted in CWE-116 (Improper Encoding or Escaping of Output): user-influenced strings were concatenated directly into generated SVG markup in the rendering builders (rect.ts, text.ts, text-decoration.ts, and the preprocessing/expansion handlers) rather than being serialized through a safe XML helper. The upstream fix for PR #814 replaced raw template-string assembly with a buildXMLString() helper, routed text nodes through escapeXMLText(), extended the embedded-SVG data-URL encoding set to also escape '&' so inner XML entities survive the enclosing SVG parse, and changed style expansion to throw on unrecognized 'internal' style properties instead of silently copying them through - closing a path where attacker-controlled style property names/values reached serialized attributes. The Next.js consumption path is significant: next/og vendors this rendering stack (the Next.js commit patches @vercel/og@0.11.1 and rebases the compiled satori bundle), so SVG injection inside generated images can execute code in the Node.js runtime. CPE data confirms both vercel:satori and vercel:next are in scope, and the independent assessment (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) treats the library-internal score as understated: the vulnerability requires attacker-controlled data to reach SVG generation (AT:P), but once that route exists no authentication is needed and the consequence in the Next.js consumer is code execution with high confidentiality, integrity, and availability impact on the subsequent system.
Know when Next gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Unauthenticated network RCE in the Node.js next/og path crossing from library into the app runtime (S:C, C/I/A:H); AC:H because it hinges on the app embedding untrusted input into SVG.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Satori is a library to convert HTML and CSS to SVG. Starting in version 0.0.27 and prior to version 0.33.5, Satori does not properly escape certain values before including them in generated SVG output. This can allow crafted values to be interpreted as SVG markup. The impact depends on how the generated SVG is consumed. Version 0.33.5 contains a patch. No complete workaround exists besides upgrading. Applications that cannot immediately upgrade should not render attacker-controlled content with Satori.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Prezi Next 1.3.101.11 has a documented purpose of creating HTML5 presentations but has SE_DEBUG_PRIVILEGE on Windows, wh
AxxonSoft Axxon Next has Directory Traversal via an initial /css//..%2f substring in a URI. Rated high severity (CVSS 7.
Prototype pollution in alibaba-fusion/next (all versions through 1.27.34) allows remote unauthenticated attackers to inj
EUVD-2026-89994
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB