Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-7167: Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial

55
This month
HIGH 7.5REMOTEUPGRADE

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

Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so that they zero fill instead of hanging in these cases. All versions of Node.js 6.x (LTS "Boron"), 8.x (LTS "Carbon"), and 9.x are vulnerable. All versions of Node.js 10.x (Current) are NOT vulnerable.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance6.7% (top 6%)
CISA exploited listNo
WeaknessCWE-119
Published2018-06-13
Last modified2026-10-08
Publisher (CNA): Node.js · Vendor: nodejs

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

nodejs node.js UPGRADE
Affected: > 6.9.0 and < 6.14.3 · >= 8.9.0 and < 8.11.3 · >= 9.0.0 and < 9.11.2
Fixed in: 6.14.3, 8.11.3, 9.11.2
Safe to downgrade to: a release before 8.9.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to 6.14.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade node.js
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade node.js
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 8.9.0 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_8.9.0> sudo apt-mark hold node.js
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_8.9.0> sudo dnf versionlock add node.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.
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-7167?

node.js: upgrade to 6.14.3, 8.11.3, 9.11.2. Exact commands for each OS are on this page.

Is CVE-2018-7167 being exploited?

CVE-2018-7167 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-7167 affect?

CVE-2018-7167 affects node.js. Severity is high (CVSS 7.5). Calling Buffer.fill() or Buffer.alloc() with some parameters can lead to a hang which could result in a Denial of Service. In order to address this vulnerability, the implementations of Buffer.alloc() and Buffer.fill() were updated so that

How urgent is CVE-2018-7167?

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

Software pages

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