CVE-2020-10531 — An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An...
An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2.7% (30-day exploitation probability)+13
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — chromium.googlesource.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Canonical | Ubuntu Linux | version 19.10version 18.04version 12.04version 14.04version 16.04 | Vulnerable | NIST National Vulnerability Database |
| Debian | Debian Linux | version 8.0version 9.0version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Fedoraproject | Fedora | version 31version 33version 30 | Vulnerable | NIST National Vulnerability Database |
| Chrome | < 80.0.3987.122 | Vulnerable | NIST National Vulnerability Database | |
| Icu-project | International Components For Unicode | ≤ 66.1 | Vulnerable | NIST National Vulnerability Database |
| Nodejs | Node.js | ≥ 10.0.0 and ≤ 10.12.0≥ 10.13.0 and < 10.21.0 | Vulnerable | NIST National Vulnerability Database |
| Opensuse | Leap | version 15.1 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Banking Extensibility Workbench | version 14.3.0version 14.4.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Enterprise Linux Desktop | version 6.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Enterprise Linux Server | version 6.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Enterprise Linux Workstation | version 6.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 6.8 | CVSS 2.0 | Medium | 8.6 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.67%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · icu-project/international components for unicode, redhat/enterprise linux desktop, redhat/enterprise linux server, redha
- CVSS changed · 8.8
- Source status changed · → Modified
- Record created in this database
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
24 on the record
- chromium.googlesource.com/chromium/deps/icu/+/9f4020916eb1f28f3666f018fdcbe6c9a37f0e08
- github.com/unicode-org/icu/pull/971
- www.oracle.com/security-alerts/cpujan2021.html
- github.com/unicode-org/icu/commit/b7d08bc04a4296982fcef8b6b8a354a9e4e7afca
- security.gentoo.org/glsa/202003-15
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOH
- bugs.chromium.org/p/chromium/issues/detail
- lists.opensuse.org/opensuse-security-announce/2020-04/msg00004.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4OOY
- www.oracle.com/security-alerts/cpuapr2022.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4OOYAM
- usn.ubuntu.com/4305-1/
- unicode-org.atlassian.net/browse/ICU-20958
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6IOHSO
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X3B5
- nvd.nist.gov/vuln/detail/CVE-2020-10531
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- github.com/advisories/GHSA-8xp2-qvq2-xhpx
- www.debian.org/security/2020/dsa-4646
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X3B5RW
- chromereleases.googleblog.com/2020/02/stable-channel-update-for-desktop_24.html
- lists.debian.org/debian-lts-announce/2020/03/msg00024.html
- access.redhat.com/errata/RHSA-2020:0738
- www.oracle.com//security-alerts/cpujul2021.html
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-110922 Use After Free in Google Chrome 4h
- Unknown CVE-2026-110920 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 4h
- Unknown CVE-2026-110919 Use After Free in Google Chrome 4h
- Unknown CVE-2026-110918 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 4h
- Unknown CVE-2026-110917 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 4h
- Unknown CVE-2026-110921 Use After Free in Google Chrome 4h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2020-10531 is "An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An...", rated High. It affects Ubuntu Linux (Canonical); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 2.67% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.