CVE-2018-6184 json
Directory traversal vulnerability in Next.js
published 8y ago modified 4mo ago also GHSA-m34x-wgrh-g897 , EUVD-2018-0160
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.1%
- EPSS 9.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /_next request namespace.
Patch / fix
- npm next 4.2.3
Is CVE-2018-6184 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
9.06% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Zeit Next.js < 4.2.3 - Local File Inclusion nuclei detection template
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, <4.2.3 |
4.2.3 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
github.com
/zeit/next.js/releases/tag/4.2.3
issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-6184
advisory
-
github.com
/advisories/GHSA-m34x-wgrh-g897
advisory
-
github.com
/vercel/next.js/releases/tag/4.2.3
web
-
github.com
/zeit/next.js
package
Sources
- CVE List CVE-2018-6184
- GitHub Advisory GHSA-m34x-wgrh-g897
- NVD CVE-2018-6184
Fencer Intel 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.