Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-6184: ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /_next request namespace.

55
This week
HIGH 7.5REMOTEDOWNGRADE

CVE-2018-6184 is a high-severity flaw (CVSS 7.5) affecting next.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /_next request namespace.

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance9.1% (top 5%)
CISA exploited listNo
WeaknessCWE-22
Published2018-01-24
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: zeit

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

zeit next.js DOWNGRADE
Affected: 4.0.0 · 4.0.1 · 4.0.2 · 4.0.3 · 4.0.4 · 4.0.5 · 4.1.0 · 4.1.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.0.0
1. Check installed version
apt-cache policy next.js || rpm -q next.js || next.js --version
2. No fixed release: DOWNGRADE to a release before 4.0.0 (Debian / Ubuntu)
apt-cache madison next.js sudo apt install next.js=<VERSION_BEFORE_4.0.0> sudo apt-mark hold next.js
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list next.js sudo dnf downgrade next.js-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add next.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-6184?

next.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-6184 being exploited?

CVE-2018-6184 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-6184 affect?

CVE-2018-6184 affects next.js. Severity is high (CVSS 7.5). ZEIT Next.js 4 before 4.2.3 has Directory Traversal under the /_next request namespace.

How urgent is CVE-2018-6184?

Priority 55/100. High severity; EPSS top 5%: very likely to be exploited; Remotely exploitable, no login, no user action

Software pages

Next.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.