How severe is GHSA-g5qg-72qw-gw5v?

GHSA-g5qg-72qw-gw5v has a CVSS score of 6.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g5qg-72qw-gw5v?

GHSA-g5qg-72qw-gw5v affects the following packages: next (npm), next (npm). Ecosystems affected: npm.

How do I fix GHSA-g5qg-72qw-gw5v?

Update next to 14.2.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5qg-72qw-gw5v is resolved across your whole dependency graph.

How do I detect GHSA-g5qg-72qw-gw5v 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-g5qg-72qw-gw5v 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-g5qg-72qw-gw5v?

O3 pinpoints whether GHSA-g5qg-72qw-gw5v 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-g5qg-72qw-gw5v actively exploited in the wild?

No public exploit code has been indexed for GHSA-g5qg-72qw-gw5v 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.

What is the EPSS score for GHSA-g5qg-72qw-gw5v?

GHSA-g5qg-72qw-gw5v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-g5qg-72qw-gw5v published, and has it been updated?

GHSA-g5qg-72qw-gw5v was published on August 29, 2025 and was last updated on February 4, 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

GHSA-g5qg-72qw-gw5v

MEDIUM

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

Also known asCVE-2025-57752

Published

Aug 29, 2025

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile+0.18%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

nextnpm

43.2Mdownloads / week

Description

A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.

All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.

More details at Vercel Changelog

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 0.9.9&&< 14.2.31	14.2.31
📦npm	`next`	≥ 15.0.0&&< 15.4.5	15.4.5

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 14.2.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5qg-72qw-gw5v 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-g5qg-72qw-gw5v 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-g5qg-72qw-gw5v. 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 Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as `Cookie` or `Authorization`), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug. All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled. More details at [Vercel Changelog](https://vercel.com/changelog/cve-2025-57752)

O3 Security · Impact-Aware SCA

Is GHSA-g5qg-72qw-gw5v in your dependencies?

O3 detects GHSA-g5qg-72qw-gw5v 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