Unicode vulnerabilitiesNone on the known-exploited list.
Unicode has 5 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is International Components for Unicode, with 2. If you run Unicode software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Unicode products have the most vulnerabilities?
International Components for Unicode leads with 2 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Unicode vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Unicode's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Unicode flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 13%CVE-2021-42574High
An issue was discovered in the Bidirectional Algorithm in the Unicode Specification through 14.0.
- 4.9%CVE-2021-42694High
An issue was discovered in the character definitions of the Unicode Specification through 14.0.
- 1.2%CVE-2020-21913Medium
International Components for Unicode (ICU-20850) v66.1 was discovered to contain a use after free bug in the pkg_createWithAssemblyCode function in the file tools/pkgdata/pkgdata.cpp.
- 0.5%CVE-2016-10610High
unicode-json is a unicode lookup table. unicode-json before 2.0.0 downloads data resources over HTTP, which leaves it vulnerable to MITM attacks.
- 0.4%CVE-2025-5222High
A stack buffer overflow was found in Internationl components for unicode (ICU ).
All Unicode products we track.
2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
- International Components for Unicodeinternational_components_for_unicode2 vulnerabilities70 versions
- Unicode-JSONunicode-json1 vulnerability28 versions
This directory lists the 2 Unicode products with at least one tracked version, of 3 in our catalogue.
Running Unicode? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An issue was discovered in the Bidirectional Algorithm in the Unicode Specification through 14.0. It permits the visual reordering of characters via control sequences, which can be used to craft source code that renders different logic than the logical ordering of tokens ingested by compilers and interpreters. Adversaries can leverage this to encode source code for compilers accepting Unicode such that targeted vulnerabilities are introduced invisibly to human reviewers. NOTE: the Unicode Consortium offers the following alternative approach to presenting this concern. An issue is noted in the nature of international text that can affect applications that implement support for The Unicode Standard and the Unicode Bidirectional Algorithm (all versions). Due to text display behavior when text includes left-to-right and right-to-left characters, the visual order of tokens may be different from their logical order. Additionally, control characters needed to fully support the requirements of bidirectional text can further obfuscate the logical order of tokens. Unless mitigated, an adversary could craft source code such that the ordering of tokens perceived by human reviewers does not match what will be processed by a compiler/interpreter/etc. The Unicode Consortium has documented this class of vulnerability in its document, Unicode Technical Report #36, Unicode Security Considerations. The Unicode Consortium also provides guidance on mitigations for this class of issues in Unicode Technical Standard #39, Unicode Security Mechanisms, and in Unicode Standard Annex #31, Unicode Identifier and Pattern Syntax. Also, the BIDI specification allows applications to tailor the implementation in ways that can mitigate misleading visual reordering in program text; see HL4 in Unicode Standard Annex #9, Unicode Bidirectional Algorithm.
- Matched to
- Unicode on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 5 published vulnerabilities across 3 products and 98 versions from Unicode.
None of Unicode's vulnerabilities is on the list of flaws known to be exploited today.
International Components for Unicode, with 2 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Unicode products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.