How severe is GHSA-2xp9-vwfh-vxw4?

No CVSS score has been assigned to GHSA-2xp9-vwfh-vxw4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2xp9-vwfh-vxw4?

GHSA-2xp9-vwfh-vxw4 affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

How do I fix GHSA-2xp9-vwfh-vxw4?

Update next to 15.5.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xp9-vwfh-vxw4 is resolved across your whole dependency graph.

How do I detect GHSA-2xp9-vwfh-vxw4 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2xp9-vwfh-vxw4 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.

How does O3 Security protect against GHSA-2xp9-vwfh-vxw4?

O3 pinpoints whether GHSA-2xp9-vwfh-vxw4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2xp9-vwfh-vxw4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2xp9-vwfh-vxw4 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-2xp9-vwfh-vxw4 published, and has it been updated?

GHSA-2xp9-vwfh-vxw4 was published on September 8, 2026 and was last updated on September 8, 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

GHSA-2xp9-vwfh-vxw4

Fix: vercel/next.js#97875

GHSA-2xp9-vwfh-vxw4 is a remote code execution vulnerability in next. O3 Security confirms whether GHSA-2xp9-vwfh-vxw4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Published

Sep 8, 2026

Updated

Sep 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 8, 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

40.6Mdownloads / week

Description

A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized.

Until a fix has propagated, optimization of AVIF files is disabled.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 10.0.0&&< 15.5.24	15.5.24
📦npm	`next`	≥ 16.0.0&&< 16.3.3	16.3.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update next to 15.5.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xp9-vwfh-vxw4 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.
How O3 protects you
O3 pinpoints whether GHSA-2xp9-vwfh-vxw4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2xp9-vwfh-vxw4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability in the underlying `libheif` library used by `sharp` which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized. Until a fix has propagated, optimization of AVIF files is disabled.

O3 Security · Impact-Aware SCA

Is GHSA-2xp9-vwfh-vxw4 in your dependencies?

O3 detects GHSA-2xp9-vwfh-vxw4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works