Unknown severity · Source severity not reportedCVE-2018-12115

CVE Program ContainerCVE-2018-12115

Answer in brief

CVE-2018-12115 records a Unknown severity vulnerability in CVE Program Container. The current sources do not mark it as known exploited. The current feed maps The Node.js Project/Node.js (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 21, 2018Updated Oct 15, 2026Source checked Oct 15, 2026First seen by HOL Oct 15, 2026Material review Oct 15, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps The Node.js Project/Node.js (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
The Node.js Project/Node.jsgeneric	All versions of Node.js prior to 6.14.4 8.11.4 and 10.9.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for The Node.js Project/Node.js.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 21, 2018
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 15, 2026

Sources and claim methodology

Upstream source description

In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second-to-last position of a buffer cause a miscalculation of the maximum length of the input bytes to be written.

Quoted source text, attributed separately from HOL analysis.