Skip to content
Fencer Vulns
high 7.5

CVE-2017-16877 in the critical feed json

Next.js Directory Traversal Vulnerability

published 2017-11-17 8 y ago modified 2026-06-17 4 mo ago also GHSA-3f5c-4qxj-vmpf , EUVD-2017-0358

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.1%
EPSS 14.1% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known, plus a Nuclei check

Summary

ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

Patch / fix

  • npm next 2.4.1
  • zeit next.js 2.4.1

Exploit prediction

14.10% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm next
>=1.0.0, <2.4.1
2.4.1

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.