Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Open Redirect in Next.js versionsGHSA-x56p-c8cg-q435

MEDIUM

GHSA-x56p-c8cg-q435 is a medium-severity (CVSS 4.7) Open Redirect vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Also known asCVE-2020-15242
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.42%0.85%1.27%0.2%0.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-x56p-c8cg-q435 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg 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
67.3Mdownloads / week

Description

Impact

  • Affected: Users of Next.js between 9.5.0 and 9.5.3
  • Not affected: Deployments on Vercel (https://vercel.com) are not affected
  • Not affected: Deployments using next export

We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.

Patches

https://github.com/vercel/next.js/releases/tag/v9.5.4

References

https://github.com/vercel/next.js/releases/tag/v9.5.4

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnext≥ 9.5.0&&< 9.5.49.5.4npm install next@9.5.4

Affected Products

1 product · 1 configurations
Application
next.jsvercel
≥ 9.5.0 && < 9.5.4
range

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

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

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### Impact - **Affected**: Users of Next.js between 9.5.0 and 9.5.3 - **Not affected**: Deployments on Vercel ([https://vercel.com](https://vercel.com)) are not affected - **Not affected**: Deployments using `next export` We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. ### Patches https://github.com/vercel/next.js/releases/tag/v9.5.4 ### References https://github.com/vercel/next.js/releases/tag/v9.5.4
O3 Security · Impact-Aware SCA

Is GHSA-x56p-c8cg-q435 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Open Redirect in Next.js versions (Medium 4.7)