NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-94545: Satori-generated SVG has improper escaping

mediumCVSS 4.0 5.3GHSA-wx4j-mvgx-mqwp

Satori, the Vercel library that turns JSX into SVG, did not escape some values before writing them into its SVG output. Crafted values could then be read as SVG markup. Satori 0.33.5 fixes it. Apps that render attacker-controlled content with Satori are affected. The related Next.js advisory covers the Node.js ImageResponse and is fixed in Next.js 16.3.6.

Published Oct 27, 2026 · Analysis Nov 1, 2026

What an attacker can do

Satori builds an SVG string from the elements you give it. Before 0.33.5 it did not properly escape certain values when writing that string. A value that carries SVG syntax could break out of its place and be parsed as markup. The fix, in pull request 814, escapes values and validates XML names and internal style fields. The advisory does not list which attributes or fields were affected.

The attacker needs a way to get their text or style values into content you pass to Satori, such as a user name, title or query parameter used in a generated social image. The effect depends on what consumes the SVG. If you serve the SVG to browsers, injected markup can run in that context. If you pass it to a rasterizer, the effect differs.

The linked Next.js advisory is more severe. It says the Node.js ImageResponse from next/og, in Next.js 16.2.0 up to 16.3.6, is affected by an upstream vulnerability. It rates that as critical remote code execution when attacker-controlled values reach SVG content, attributes or styles. It does not name Satori as the upstream component. The Edge ImageResponse is not affected. The Satori advisory itself rates this medium and gives no code execution claim.

Who is affected

satori from 0.0.27 up to but not including 0.33.5. Next.js apps using the Node.js ImageResponse from next/og on 16.2.0 up to 16.3.6 are covered by the separate Next.js advisory. Check both:

npm ls satori next

Then search your code for places where user input flows into JSX passed to Satori or ImageResponse.

satori

Ecosystem
npm
Affected
>= 0.0.27, < 0.33.5
Fixed in
0.33.5
Check
npm ls satori

How to fix it

Upgrade satori to 0.33.5:

npm install [email protected]

For Next.js, upgrade to 16.3.6 with npm install [email protected]. The Satori advisory says no complete workaround exists. Until you upgrade, do not render attacker-controlled content with Satori. The Next.js advisory gives the same advice for SVG content, attributes and styles in the Node.js ImageResponse.

How to tell if you were hit

Audit routes that generate images, such as OG image endpoints, and look at which request parameters reach Satori or ImageResponse. In access logs, look for parameters on those routes that contain angle brackets, quotes, or SVG tag names. Inspect generated SVG files or cached images for unexpected elements or attributes, such as script or event handlers.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

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.

Workaround

No complete workaround exists besides upgrading. Applications that cannot immediately upgrade should not render attacker-controlled content with Satori.

Credited to RaghavMaheshwari124, rafabd1.

Questions

Is every Satori user affected?

Only if attacker-controlled values reach Satori. The advisory says the impact depends on how the generated SVG is used, and that apps not rendering attacker-controlled content are not at risk from this.

Is there a workaround?

No complete one. The advisory says to upgrade, and until then to avoid rendering attacker-controlled content with Satori.

Does this affect Next.js ImageResponse?

The Next.js advisory says the Node.js ImageResponse in 16.2.0 up to 16.3.6 is affected by an upstream flaw, fixed in 16.3.6. The Edge ImageResponse is not affected.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology