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

> Attackers can inject malicious SVG markup via improper escaping in Satori, potentially leading to code execution when rendered.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-wx4j-mvgx-mqwp

## What is CVE-2026-94545?

CVE-2026-94545 is a medium-severity cross-site scripting vulnerability in vercel next, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-94545?

2 open source packages ship an affected version, including satori.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `satori` | npm | From 0.0.27 | 0.33.5 |
| `satori` | npm | From 0.0.27 | 0.33.5 |

## How do I fix CVE-2026-94545?

Upgrade satori to 0.33.5 or later.

## Is CVE-2026-94545 being exploited?

There is no known exploitation of CVE-2026-94545 in the wild and no public exploit code.

Public exploit code:

- Next.js RCE (github_poc): https://github.com/EQSTLab/CVE-2026-94545
- CVE-2026-94545 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-94545
- CVE-2026-94545 / GHSA-vcvr-r3jv-pc5j — Next.js next/og ImageResponse SVG injection (Satori, GHSA-wx4j-mvgx-mqwp): isolated Docker validation lab with vulnerable (16.3.5) vs patched (16.3.6) controls, non-destructive Python scanner with pixel-level PNG evidence, and root-cause analysis of the upstream Satori fix. Authorized security research only. (github_poc): https://github.com/Hassham1/CVE-2026-94545-nextjs-og-poc
- Next.js next/og unauthenticated RCE (CVE-2026-94545) - PoC (github_poc): https://github.com/MRdark-ops/CVE-2026-94545-

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94545 and fix it if it is affected.

What it is: CVE-2026-94545 is a medium-severity cross-site scripting vulnerability in vercel next, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-94545 in the wild and no public exploit code.

Affected packages and fixed versions:
- satori (npm): affected from 0.0.27; fixed in 0.33.5
- satori (npm): affected from 0.0.27; fixed in 0.33.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94545/ (Markdown: https://insights.sbomify.com/CVE-2026-94545/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94545
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94545
- OSV: https://osv.dev/vulnerability/CVE-2026-94545

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94545/
Summaries are generated and may contain mistakes; the official description above is the record.