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

GHSA-x56p-c8cg-q435

MEDIUM

GHSA-x56p-c8cg-q435 is a medium-severity (CVSS 4.7) Open Redirect vulnerability in next. O3 Security confirms whether GHSA-x56p-c8cg-q435 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Open Redirect in Next.js versions

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

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
55.0Mdownloads / 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
📦npmnext9.5.0&&< 9.5.49.5.4

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

  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

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-x56p-c8cg-q435 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-x56p-c8cg-q435. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

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