How severe is CVE-2015-8548?

CVE-2015-8548 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2015-8548 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2015-8548?

CVE-2015-8548 primarily affects Google V8. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2015-8548?

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-8548 published?

CVE-2015-8548 was published on 2015-12-14 and last updated on 2026-06-17.

CVE-2015-8548

CVE-2015-8548 is a critical-severity vulnerability in Google V8 with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 1% (64th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Google V8
Published: 2015-12-14
Last modified: 2026-06-17

Description

Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow attackers to cause a denial of service or possibly have other impact via unknown vectors, a different issue than CVE-2015-8478.

Frequently asked questions

What is CVE-2015-8548?: Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow attackers to cause a denial of service or possibly have other impact via unknown vectors, a different issue than CVE-2015-8478.
How severe is CVE-2015-8548?: CVE-2015-8548 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2015-8548 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-8548?: CVE-2015-8548 primarily affects Google V8. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-8548?: 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-8548 published?: CVE-2015-8548 was published on 2015-12-14 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:google:v8:*:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

More vulnerabilities in Google V8

CVE-2014-1704 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google V8 before 3.23.17.18, as used in Google Chrome before 33.0.1750.149,…
CVE-2016-2843 — Critical (CVSS 9.8): Multiple unspecified vulnerabilities in Google V8 before 4.9.385.26, as used in Google Chrome before 49.0.2623.75,…
CVE-2009-2555 — Critical (CVSS 9.3): Heap-based buffer overflow in src/jsregexp.cc in Google V8 before 1.1.10.14, as used in Google Chrome before…
CVE-2016-5129 — High (CVSS 8.8): Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed…
CVE-2016-5128 — High (CVSS 8.8): 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-1678 — High (CVSS 8.8): objects.cc in Google V8 before 5.0.71.32, as used in Google Chrome before 51.0.2704.63, does not properly restrict lazy…

All CVEs affecting Google V8 →