CVE-2015-8857

CVE-2015-8857 is a critical-severity vulnerability in Uglifyjs Project Uglifyjs with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

The uglify-js package before 2.4.24 for Node.js does not properly account for non-boolean values when rewriting boolean expressions, which might allow attackers to bypass security mechanisms or possibly have unspecified other impact by leveraging improperly rewritten Javascript.

Frequently asked questions

What is CVE-2015-8857?
The uglify-js package before 2.4.24 for Node.js does not properly account for non-boolean values when rewriting boolean expressions, which might allow attackers to bypass security mechanisms or possibly have unspecified other impact by leveraging improperly rewritten Javascript.
How severe is CVE-2015-8857?
CVE-2015-8857 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2015-8857 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-8857?
CVE-2015-8857 affects Uglifyjs Project Uglifyjs. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2015-8857?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2015-8857 published?
CVE-2015-8857 was published on 2017-01-23 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Uglifyjs Project Uglifyjs

All CVEs affecting Uglifyjs Project Uglifyjs →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →