Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2014-9654

icu: insufficient size limit checks in regular expression compiler

Overview

Published
24 Apr 2017
Modified
13 May 2026
Critical CVE
0 Registry packages
5 OS packages
4 Linux distributions
Yes Fix available

Description

The Regular Expressions package in International Components for Unicode (ICU) for C/C++ before 2014-12-03, as used in Google Chrome before 40.0.2214.91, calculates certain values without ensuring that they can be represented in a 24-bit field, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted string, a related issue to CVE-2014-7923.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.0 base score, scored by NVD.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 7 fixes

Red Hat 1 release · 1 package

wont fix 1
icu
Red Hat fixes for CVE-2014-9654
ReleasePackageFixed in
7 icu +3 wont fix

debian 4 releases · 1 package

fixed 4
icu
debian fixes for CVE-2014-9654
ReleasePackageFixed in
11 icu 52.1-7.1
12 icu 52.1-7.1
13 icu 52.1-7.1
14 icu 52.1-7.1

echo 1 release · 1 package

fixed 1
icu
echo fixes for CVE-2014-9654
ReleasePackageFixed in
icu 52.1-7.1

root.io debian 1 release · 1 package

fixed 1
rootio-icu
root.io debian fixes for CVE-2014-9654
ReleasePackageFixed in
12 rootio-icu 52.1-7.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.