Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.5 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.

Published by the source

22 Oct 2026, 15:52 UTC

Last modified by the source

22 Oct 2026, 16:00 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 5 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2464-fhr4-w9xw

2. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2464-fhr4-w9xw

3. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-2464-fhr4-w9xw

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-2464-fhr4-w9xw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2464-fhr4-w9xw

Advisory: Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
IDs: GHSA-2464-fhr4-w9xw
Record: https://patchnext.com/advisories/ghsa-2464-fhr4-w9xw (revision 5, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: next 16.4.1, 15.5.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm next: affected >= 10.0.0, <= 15.5.27; >= 16.0.0, <= 16.4.0; fixed in 16.4.1, 15.5.28

## Suggested inspection (read-only)
- `npm ls next --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on next.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2464-fhr4-w9xw (GitHub-reviewed advisory GHSA-2464-fhr4-w9xw lists affected ranges: npm next >=10.0.0 =16.0.0 <=16.4.0)
- Verified: https://osv.dev/vulnerability/GHSA-2464-fhr4-w9xw (OSV record GHSA-2464-fhr4-w9xw lists affected ranges: npm next >=10.0.0 =16.0.0 <16.4.1 (fixed))

Commands are suggestions: review each one before running it.