How severe is GHSA-c59h-r6p8-q9wc?

No CVSS score has been assigned to GHSA-c59h-r6p8-q9wc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c59h-r6p8-q9wc?

GHSA-c59h-r6p8-q9wc affects the following packages: next (npm). Ecosystems affected: npm.

How do I fix GHSA-c59h-r6p8-q9wc?

Update next to 13.4.20-canary.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c59h-r6p8-q9wc is resolved across your whole dependency graph.

How do I detect GHSA-c59h-r6p8-q9wc 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-c59h-r6p8-q9wc 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-c59h-r6p8-q9wc?

O3 pinpoints whether GHSA-c59h-r6p8-q9wc 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-c59h-r6p8-q9wc actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-c59h-r6p8-q9wc, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-c59h-r6p8-q9wc?

GHSA-c59h-r6p8-q9wc has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 66th 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-c59h-r6p8-q9wc published, and has it been updated?

GHSA-c59h-r6p8-q9wc was published on October 22, 2023 and was last updated on November 8, 2023. 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-c59h-r6p8-q9wc

Next.js missing cache-control header may lead to CDN caching empty reply

Also known asCVE-2023-46298

Published

Oct 22, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk66th percentile+0.91%

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

1 pkg affected

📦next

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 0.9.9&&< 13.4.20-canary.13	13.4.20-canary.13

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Next.js before 13.4.20-canary.13 lacks a cache-control header and thus e…

github.comNVDOct 2023

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 13.4.20-canary.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c59h-r6p8-q9wc 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-c59h-r6p8-q9wc 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-c59h-r6p8-q9wc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-c59h-r6p8-q9wc in your dependencies?

O3 detects GHSA-c59h-r6p8-q9wc 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