CVE-2017-16877: ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing att

Q: How do I fix CVE-2017-16877?

next.js: upgrade to 2.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2017-16877 being exploited?

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

Q: What does CVE-2017-16877 affect?

CVE-2017-16877 affects next.js. Severity is high (CVSS 7.5). ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

Q: How urgent is CVE-2017-16877?

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

This week

HIGH 7.5REMOTEUPGRADE

CVE-2017-16877 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 before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	14.1% (top 3%)
CISA exploited list	No
Weakness	CWE-22
Published	2017-11-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: zeit

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

Am I affected?

Timeline

2017-11-17 17:29 UTCPublished CVE record published
2026-06-17 01:10 UTCUpdated Record last modified

zeit next.js UPGRADE

Affected: < 2.4.1

Fixed in: 2.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy next.js || rpm -q next.js || next.js --version

2. UPGRADE to 2.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade next.js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade next.js

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

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

Nuclei scan template: Nextjs <2.4.1 - Local File Inclusion

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-2017-16877?

next.js: upgrade to 2.4.1. Exact commands for each OS are on this page.

Is CVE-2017-16877 being exploited?

CVE-2017-16877 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-2017-16877 affect?

CVE-2017-16877 affects next.js. Severity is high (CVSS 7.5). ZEIT Next.js before 2.4.1 has directory traversal under the /_next and /static request namespace, allowing attackers to obtain sensitive information.

How urgent is CVE-2017-16877?

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

Software pages

Next.js vulnerabilities

Related CVEs

CVE-2026-44572 LOW 3.7 UPGRADE Next.js is a React framework for building full-stack web applications
CVE-2026-44575 HIGH 7.5 UPGRADE Next.js is a React framework for building full-stack web applications
CVE-2026-44573 HIGH 7.5 UPGRADE Next.js is a React framework for building full-stack web applications
CVE-2026-44574 HIGH 8.1 UPGRADE Next.js is a React framework for building full-stack web applications
CVE-2026-44577 MEDIUM 5.9 UPGRADE Next.js is a React framework for building full-stack web applications

References

← Back to latest CVEs