---
title: "GHSA-7qx7-33qx-rqx2: Next.js: SVG rejection bypass in the image optimization"
description: "Moderate severity. Next.js: SVG rejection bypass in the image optimization. Affects next; fixed in 16.4.5."
url: https://inlinr.com/advisories/GHSA-7qx7-33qx-rqx2
lang: en
---

[Packages](https://inlinr.com/packages) / [next](https://inlinr.com/packages/next) / [Security](https://inlinr.com/packages/next/security)

Moderate Vulnerability GHSA-7qx7-33qx-rqx2 CVE-2026-119347 Published 19 Nov 2026

# Next.js: SVG rejection bypass in the image optimization

Your version 

Affected releases · [next](https://inlinr.com/packages/next)

- 16.x 16.0.0 – 16.4.4 Fixed in 16.4.5
- 15.x 15.0.0 – 15.5.28 Fixed in 15.5.29

On 16.x, the newest line:

```
npm install next@16.4.5
```

Every release on a timeline

16.x 

1. Affected

16.0.0 – 16.4.4  
47 releases
2. Fixed

16.4.5 – 16.4.6  
2 releases

15.x 

1. Affected

15.0.0 – 15.5.28  
82 releases
2. Fixed

15.5.29  
1 release

428 stable releases of next, oldest to newest, one row per major.

## What happens

On self-hosted deployments, the Next.js image optimizer (`/_next/image`) can be made to process an attacker-supplied SVG even when SVG support is disabled with `dangerouslyAllowSVG: false` (the default). This reaches an SVG parser the application intended to keep disabled, increasing exposure to denial of service and SVG decoder vulnerabilities.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: none
- **Integrity**: none
- **Availability**: low

CVSS:4.0/​AV:N/​AC:L/​AT:N/​PR:N/​UI:N/​VC:N/​VI:N/​VA:L/​SC:N/​SI:N/​SA:N

## References

- [Reference](https://github.com/vercel/next.js/security/advisories/GHSA-7qx7-33qx-rqx2 "https://github.com/vercel/next.js/security/advisories/GHSA-7qx7-33qx-rqx2")  
github.com/vercel/next.js/security/advisories/G…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-119347 "https://nvd.nist.gov/vuln/detail/CVE-2026-119347")  
nvd.nist.gov/vuln/detail/CVE-2026-119347
- [Fix commit](https://github.com/vercel/next.js/commit/4f133352e639589ad9872b9b55307b89b258e41b "https://github.com/vercel/next.js/commit/4f133352e639589ad9872b9b55307b89b258e41b")  
4f13335
- [Fix commit](https://github.com/vercel/next.js/commit/e66e656e7d423a828bdca5f87e82cef7038c57a6 "https://github.com/vercel/next.js/commit/e66e656e7d423a828bdca5f87e82cef7038c57a6")  
e66e656
- [Package](https://github.com/vercel/next.js "https://github.com/vercel/next.js")  
github.com/vercel/next.js
- [Reference](https://github.com/vercel/next.js/releases/tag/v15.5.29 "https://github.com/vercel/next.js/releases/tag/v15.5.29")  
github.com/vercel/next.js/releases/tag/v15.5.29
- [Reference](https://github.com/vercel/next.js/releases/tag/v16.4.5 "https://github.com/vercel/next.js/releases/tag/v16.4.5")  
github.com/vercel/next.js/releases/tag/v16.4.5
- [Reference](https://nextjs.org/blog/november-2026-security-release "https://nextjs.org/blog/november-2026-security-release")  
nextjs.org/blog/november-2026-security-release

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
