How severe is GHSA-2464-fhr4-w9xw?

No CVSS score has been assigned to GHSA-2464-fhr4-w9xw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2464-fhr4-w9xw?

GHSA-2464-fhr4-w9xw affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

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

Update next to 15.5.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2464-fhr4-w9xw is resolved across your whole dependency graph.

How do I detect GHSA-2464-fhr4-w9xw in my npm dependencies?

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.

How do I mitigate GHSA-2464-fhr4-w9xw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2464-fhr4-w9xw actively exploited in the wild?

No public exploit code has been indexed for GHSA-2464-fhr4-w9xw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2464-fhr4-w9xw published, and has it been updated?

GHSA-2464-fhr4-w9xw was published on October 22, 2026 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

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

Fix: vercel/next.js@5e3b687

GHSA-2464-fhr4-w9xw is a remote code execution vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Published

Oct 22, 2026

Updated

Oct 22, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

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.

61Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

nextnpm

44.6Mdownloads / week

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 10.0.0&&< 15.5.28	15.5.28`npm install next@15.5.28`
📦npm	`next`	≥ 16.0.0&&< 16.4.1	16.4.1`npm install next@16.4.1`

Detection & mitigation playbook

Open-source dependency

Detect
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.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2464-fhr4-w9xw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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.

O3 Security · Impact-Aware SCA

Is GHSA-2464-fhr4-w9xw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works