Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
next/og ImageResponse can run attacker code
published 8 days ago
Summary
The ImageResponse feature used by next/og can let a malicious user cause your server to run their own code if you insert unchecked data into the generated SVG. This affects applications that build images with user‑supplied values using this function. Update to the latest version or stop inserting external data into the SVG when using ImageResponse.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Debian:13 | docker hardened images | homepage | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | langfuse-3 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | supabase-studio | All versions |
Original advisory text
## Impact
## Impact
The Node.js `ImageResponse` implementation from `next/og` is affected by an upstream vulnerability. This can lead to remote code execution.
Affected applications pass attacker-controlled values into SVG content, attributes, or styles during image generation:
```tsx
import { ImageResponse } from 'next/og'
export async function GET(request: Request) {
const value = new URL(request.url).searchParams.get('value') ?? ''
return new ImageResponse(
<svg width="1200" height="630">
<title>{value}</title>
</svg>
)
}
```
Applications using the Edge `ImageResponse` implementation, or applications that do not pass attacker-controlled values into SVG content, attributes, or styles, are not affected.
## Workaround
If upgrading is not immediately possible, do not pass attacker-controlled values into SVG content, attributes, or styles rendered by the Node.js `ImageResponse` implementation from `next/og`.
The Node.js `ImageResponse` implementation from `next/og` is affected by an upstream vulnerability. This can lead to remote code execution.
Affected applications pass attacker-controlled values into SVG content, attributes, or styles during image generation:
```tsx
import { ImageResponse } from 'next/og'
export async function GET(request: Request) {
const value = new URL(request.url).searchParams.get('value') ?? ''
return new ImageResponse(
<svg width="1200" height="630">
<title>{value}</title>
</svg>
)
}
```
Applications using the Edge `ImageResponse` implementation, or applications that do not pass attacker-controlled values into SVG content, attributes, or styles, are not affected.
## Workaround
If upgrading is not immediately possible, do not pass attacker-controlled values into SVG content, attributes, or styles rendered by the Node.js `ImageResponse` implementation from `next/og`.
References
- https://scout.docker.com/v/DHI-r3w2-pynz-zx4x-5m5v Vendor Advisory
- https://github.com/advisories/GHSA-vcvr-r3jv-pc5j Vendor Advisory
- https://github.com/vercel/satori/security/advisories/GHSA-wx4j-mvgx-mqwp Vendor Advisory
- https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j Vendor Advisory
- https://github.com/vercel/next.js/commit/868fad38690d72088868f299fa2bef339b26838... Patch
- https://github.com/vercel/next.js/releases/tag/v16.3.6 URL
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Timeline
Published13 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-r3w2-pynz-zx4x-5m5v · OSV
Track software like this
Free during beta