CVE-2016-2052

Multiple unspecified vulnerabilities in HarfBuzz before 1.0.6, as used in Google Chrome before 48.0.2564.82, allow attackers to cause a denial of service or possibly have other impact via crafted data, as demonstrated by a buffer over-read resulting from an inverted length check in hb-ot-font.cc, a different issue than CVE-2015-8947.

Published: 2016-01-25 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-2052 is rated Moderate Risk (50.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.97%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-2052

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.41% 0.97% +0.56%
2 2026-01-14 0.46% 0.41% -0.05%
3 2025-03-30 — 0.46% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-2052

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 4.7 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2016-2052

OS Trackers for CVE-2016-2052

vendor priority summary link
debian not yet assigned CVE-2016-2052 not yet assigned priority: Debian including 1 source packages (harfbuzz), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-2052
gentoo normal CVE-2016-2052: 1 GLSA(s) (201701-76), 1 atom(s) (media-libs/harfbuzz); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-2052
redhat medium — https://access.redhat.com/security/cve/CVE-2016-2052
ubuntu medium CVE-2016-2052 medium priority: Ubuntu including 3 source packages (chromium-browser, harfbuzz, oxide-qt), 24 status rows across 8 suites (precise, trusty, upstream, vivid, wily, xenial, yakkety, zesty): released 16, ignored 3, not-affected 3, DNE 2. https://ubuntu.com/security/CVE-2016-2052

Affected software / configurations for CVE-2016-2052

Vendor Product Version Raw CPE
harfbuzz_project harfbuzz <= 1.0.5 cpe:2.3:a:harfbuzz_project:harfbuzz:*:*:*:*:*:*:*:*
google chrome <= 47.0.2526.106 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2016-2052

cvelogic Threat Intelligence