CVE Intelligence
High Memory corruption

CVE-2018-12115 — In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding ...

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.

Published Aug 21, 2018 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: nodejs

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 8.1% (30-day exploitation probability)+14
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
8.09%
ahead of 95% of scored CVEs · Oct 15, 2026
Affects
Nodejs
Node.js and 1 more
CVSS base
7.5
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Nodejs Node.js, Red Hat Openshift Container Platform, The Node.js Project Node.js).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. EPSS ahead of 95% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Nodejs Node.js < 6.14.4≥ 8.0.0 and < 8.11.4≥ 10.0.0 and < 10.9.0 Vulnerable NIST National Vulnerability Database
Red Hat Openshift Container Platform version 3.11 Vulnerable NIST National Vulnerability Database
The Node.js Project Node.js version All versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.0 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · the node.js project/node.js
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Affected products added · nodejs/node.js, redhat/openshift container platform
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • 2018
  • CVE published
    Aug 21, 2018 · nodejs

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

Elsewhere on this site

Nodejs
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-104046 Sssd: sssd: denial of service via incomplete identity provider authentication requests 9d
  • CVE-2026-104045 Sssd: sssd: denial of service via race condition in autofs responder 9d
  • CVE-2026-104047 Sssd: sssd: information disclosure via query injection in entra id lookups 9d
  • CVE-2026-104048 Sssd: sssd: authorization bypass via cross-domain username collision in hbac evaluation 9d
  • CVE-2026-90462 Sssd: sssd: fail-open in ldap ppolicy access check allows continued authorization 23d
  • CVE-2026-90996 Sssd: sssd: denial of service in nss responder via crafted zero-length requests Sep 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-12115 is "In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding ...", rated High. It affects Node.js (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 8.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.