CVE-2015-5380: The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.1

Q: How do I fix CVE-2015-5380?

v8: mitigate or apply the listed mitigation; io.js: upgrade to newer than 1.8.2; node.js: upgrade to newer than 0.12.5. Exact commands for each OS are on this page.

Q: Is CVE-2015-5380 being exploited?

CVE-2015-5380 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-2015-5380 affect?

CVE-2015-5380 affects v8, io.js, node.js. Severity is high (CVSS 7.5). The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.x before 2.3.3, and other products, does not verify that there is memory available for a UTF-16 surr

This month

HIGH 7.5MITIGATEUPGRADEUPGRADE

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

The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.x before 2.3.3, and other products, does not verify that there is memory available for a UTF-16 surrogate pair, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted byte sequence.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	3.0% (top 13%)
CISA exploited list	No
Weakness	CWE-119
Published	2015-07-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: google · iojs · nodejs

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

Am I affected?

Timeline

2015-07-09 10:59 UTCPublished CVE record published
2026-06-17 00:29 UTCUpdated Record last modified

google v8 MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy v8 || rpm -q v8 || v8 --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

iojs io.js UPGRADE

Affected: <= 1.8.2 · 2.0.0 · 2.0.1 · 2.0.2 · 2.1.0 · 2.2.0 · 2.2.1 · 2.3.0

Fixed in: newer than 1.8.2

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.8.2 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade io.js

Note

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

nodejs node.js UPGRADE

Affected: <= 0.12.5

Fixed in: newer than 0.12.5

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 0.12.5 (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.

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-2015-5380?

v8: mitigate or apply the listed mitigation; io.js: upgrade to newer than 1.8.2; node.js: upgrade to newer than 0.12.5. Exact commands for each OS are on this page.

Is CVE-2015-5380 being exploited?

CVE-2015-5380 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-2015-5380 affect?

CVE-2015-5380 affects v8, io.js, node.js. Severity is high (CVSS 7.5). The Utf8DecoderBase::WriteUtf16Slow function in unicode-decoder.cc in Google V8, as used in Node.js before 0.12.6, io.js before 1.8.3 and 2.x before 2.3.3, and other products, does not verify that there is memory available for a UTF-16 surr

How urgent is CVE-2015-5380?

Priority 48/100. High severity

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2026-85046 HIGH 8.8 EXPLOITED UPGRADE UPGRADE Google Chromium V8 Type Confusion Vulnerability
CVE-2016-5129 HIGH 8.8 DOWNGRADE UPGRADE Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trim
CVE-2016-5128 HIGH 8.8 UPGRADE DOWNGRADE objects.cc in Google V8 before 5.2.361.27, as used in Google Chrome before 52.0.2743.82, does not prevent API
CVE-2016-3679 HIGH 8.8 UPGRADE MITIGATE Multiple unspecified vulnerabilities in Google V8 before 4.9.385.33, as used in Google Chrome before 49.0.2623
CVE-2016-2843 CRITICAL 9.8 UPGRADE UPGRADE Multiple unspecified vulnerabilities in Google V8 before 4.9.385.26, as used in Google Chrome before 49.0.2623

References

← Back to latest CVEs