Next.js: SVG rejection bypass in the image optimizationGHSA-7qx7-33qx-rqx2
Fix: vercel/next.js@4f13335GHSA-7qx7-33qx-rqx2 is a CWE-1287 vulnerability in next. A fix is available for next — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7qx7-33qx-rqx2.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
nextnpmDescription
Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.29 and 16.4.5, the /_next/image optimizer in self-hosted Next.js deployments can process attacker-supplied SVG content even when dangerouslyAllowSVG is false, which is the default. The SVG reaches a parser that the application intended to keep disabled, increasing exposure to denial of service and vulnerabilities in SVG decoding. This issue is fixed in versions 16.4.5 and 15.5.29.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | next | ≥ 15.0.0&&< 15.5.29 | 15.5.29npm install next@15.5.29 |
| 📦npm | next | ≥ 16.0.0&&< 16.4.5 | 16.4.5npm install next@16.4.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next to 15.5.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7qx7-33qx-rqx2 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as Moderate impact because an unauthenticated remote attacker can trigger resource consumption leading to denial of service in the image optimization service, but cannot compromise system confidentiality or integrity. In affected deployments, the image optimizer unexpectedly processes…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for GHSA-7qx7-33qx-rqx2 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-7qx7-33qx-rqx2 in your dependencies?
Find it across npm, including transitive dependencies.