# GHSA-2464-fhr4-w9xw: Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026

## What is GHSA-2464-fhr4-w9xw?

GHSA-2464-fhr4-w9xw is a vulnerability in next, published on 22 Oct 2026. 

### Official description

## Impact

A memory-related vulnerability has been discovered in an upstream library used for Image Optimization can lead to possible remote code execution (RCE) when Next.js runs on glibc-based Linux.

## Workaround

Ensure the version of `sharp` used by Next.js is greater than or equal to `0.35.5`. Fresh installs automatically get a fixed version of `sharp`.
Upgrading Next.js to the patched versions will ensure package managers automatically provide a fixed version of `sharp` to Next.js.

## Which versions are affected by GHSA-2464-fhr4-w9xw?

4 open source packages ship an affected version, including next.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 10.0.0 | 15.5.28 |
| `next` | npm | From 10.0.0 | 15.5.28 |
| `next` | npm | From 16.0.0 | 16.4.1 |
| `next` | npm | From 16.0.0 | 16.4.1 |

## How do I fix GHSA-2464-fhr4-w9xw?

Upgrade next to a fixed version for your release line: 15.5.28 or 16.4.1.

## Is GHSA-2464-fhr4-w9xw being exploited?

There is no known exploitation of GHSA-2464-fhr4-w9xw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2464-fhr4-w9xw and fix it if it is affected.

What it is: GHSA-2464-fhr4-w9xw is a vulnerability in next, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of GHSA-2464-fhr4-w9xw in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 10.0.0; fixed in 15.5.28
- next (npm): affected from 10.0.0; fixed in 15.5.28
- next (npm): affected from 16.0.0; fixed in 16.4.1
- next (npm): affected from 16.0.0; fixed in 16.4.1

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/GHSA-2464-fhr4-w9xw/ (Markdown: https://insights.sbomify.com/GHSA-2464-fhr4-w9xw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2464-fhr4-w9xw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2464-fhr4-w9xw/
Summaries are generated and may contain mistakes; the official description above is the record.