Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
Next.js on Linux could run attacker code via image library
published 10 days ago
Summary
Docker images that run Next.js on glibc-based Linux use an image optimization library that may allow an attacker to run their own code. Upgrade the Sharp package to version 0.35.5 or later, or update Next.js to a version that includes the newer Sharp. After updating, the risk is removed.
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-2 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | langfuse-3 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | langfuse-worker-3 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | langfuse-worker-4 | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | supabase-studio | All versions |
Original advisory text
## Impact
## 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.
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.
References
- https://scout.docker.com/v/DHI-jzyn-k6ui-zz6p-w34s Vendor Advisory
- https://github.com/advisories/GHSA-2464-fhr4-w9xw Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-96889 Vendor Advisory
- https://github.com/vercel/next.js/security/advisories/GHSA-2464-fhr4-w9xw Vendor Advisory
- https://github.com/vercel/next.js/commit/9571ec899f063df6533351bec390ccb2cc0af6a... Patch
- https://github.com/vercel/next.js/commit/5e3b687b5edb868b064bdc058d768a7021e7f6a... Patch
- https://github.com/vercel/next.js/releases/tag/v16.4.1 URL
- https://github.com/vercel/next.js/releases/tag/v15.5.28 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
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-jzyn-k6ui-zz6p-w34s · OSV
Track software like this
Free during beta