CVE-2021-42574

HIGHNVD 8.38.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 12.2%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 12%CVSS: 8.3Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
95.7%
KEV
Not listed

Published

November 1, 2021

Last Modified

November 21, 2024

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatllvm-toolset:rhel8-8050020211110163227.c53685002021-11-18redhat
redhatdevtoolset-11-binutils-0:2.36.1-1.el7.12021-11-18redhat
redhatdevtoolset-11-annobin-0:9.82-1.el7.12021-11-18redhat
redhatdevtoolset-10-binutils-0:2.35-5.el7.32021-11-17redhat
redhatdevtoolset-10-annobin-0:9.23-4.el7.12021-11-17redhat
redhatrust-toolset-1.54-rust-0:1.54.0-4.el7_92021-11-16redhat
redhatgcc-toolset-10-binutils-0:2.35-8.el8_5.62021-11-15redhat
redhatdevtoolset-11-gcc-0:11.2.1-1.2.el72021-11-15redhat
redhatbinutils-0:2.30-93.el8_4.22021-11-10redhat
redhatgcc-toolset-10-gcc-0:10.3.1-1.2.el8_52021-11-10redhat
redhatbinutils-0:2.30-108.el8_5.12021-11-10redhat
redhatgcc-toolset-10-annobin-0:9.29-1.el8_4.12021-11-10redhat
redhatbinutils-0:2.30-73.el8_2.12021-11-10redhat
redhatgcc-toolset-11-gcc-0:11.2.1-1.2.el8_52021-11-10redhat
redhatgcc-toolset-10-annobin-0:9.29-1.el8_5.22021-11-10redhat
redhatannobin-0:9.72-1.el8_5.22021-11-10redhat
redhatrust-toolset:rhel8-8050020211027231136.5c15747c2021-11-10redhat
redhatbinutils-0:2.30-58.el8_1.32021-11-10redhat
redhatannobin-0:8.90-1.el8_2.12021-11-10redhat
redhatgcc-toolset-10-binutils-0:2.35-8.el8_4.52021-11-10redhat
redhatgcc-toolset-11-annobin-0:9.85-1.el8_5.12021-11-10redhat
redhatannobin-0:9.50-1.el8_4.12021-11-10redhat
redhatgcc-toolset-11-binutils-0:2.36.1-1.el8_5.12021-11-10redhat
redhatgcc-0:8.5.0-4.el8_52021-11-10redhat
redhatannobin-0:8.78-1.el8_1.12021-11-10redhat
redhatbinutils-0:2.27-34.base.el7_6.42021-11-01redhat
redhatbinutils-0:2.23.52.0.1-55.el7_2.42021-11-01redhat
redhatbinutils-0:2.25.1-22.base.el7_3.32021-11-01redhat
redhatbinutils-0:2.27-44.base.el7_9.12021-11-01redhat
redhatbinutils-0:2.25.1-32.base.el7_4.52021-11-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 14:16 UTCEPSS rescore
  3. 2026-07-23 02:04 UTCEG score recompute
  4. 2026-07-22 22:51 UTCEG score recompute
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-20 17:05 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-18 10:02 UTCEPSS rescore
  11. 2026-07-18 10:02 UTCEPSS rescore
  12. 2026-07-18 08:59 UTCOSV refresh
  13. 2026-07-16 17:00 UTCEPSS rescore
  14. 2026-07-16 17:00 UTCEPSS rescore
  15. 2026-07-15 16:55 UTCEPSS rescore
  16. 2026-07-15 16:55 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-13 22:27 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-11 08:25 UTCEPSS rescore
  25. 2026-07-09 19:07 UTCEPSS rescore
Show 72 more
  1. 2026-07-07 13:43 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-06 02:21 UTCEPSS rescore
  5. 2026-07-06 02:21 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-05 02:28 UTCEPSS rescore
  8. 2026-07-02 16:57 UTCEPSS rescore
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-30 08:00 UTCOSV refresh
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-27 03:06 UTCEPSS rescore
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-25 13:48 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-22 14:24 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
  26. 2026-06-18 17:51 UTCEPSS rescore
  27. 2026-06-18 17:51 UTCEPSS rescore
  28. 2026-06-17 17:51 UTCEPSS rescore
  29. 2026-06-17 17:51 UTCEPSS rescore
  30. 2026-06-17 17:51 UTCEPSS rescore
  31. 2026-06-16 17:51 UTCEPSS rescore
  32. 2026-06-16 17:51 UTCEPSS rescore
  33. 2026-06-15 17:46 UTCEPSS rescore
  34. 2026-06-14 23:15 UTCEPSS rescore
  35. 2026-06-14 23:15 UTCEPSS rescore
  36. 2026-06-12 23:10 UTCEPSS rescore
  37. 2026-06-12 18:10 UTCOSV refresh
  38. 2026-06-11 13:58 UTCEPSS rescore
  39. 2026-06-11 13:58 UTCEPSS rescore
  40. 2026-06-10 22:16 UTCEPSS rescore
  41. 2026-06-10 22:16 UTCEPSS rescore
  42. 2026-06-10 13:20 UTCEPSS rescore
  43. 2026-06-07 15:23 UTCEPSS rescore
  44. 2026-06-07 15:23 UTCEPSS rescore
  45. 2026-06-06 13:46 UTCEPSS rescore
  46. 2026-06-06 13:46 UTCEPSS rescore
  47. 2026-06-05 22:45 UTCEPSS rescore
  48. 2026-06-05 06:09 UTCEPSS rescore
  49. 2026-06-05 06:09 UTCEPSS rescore
  50. 2026-06-04 13:10 UTCEPSS rescore
  51. 2026-06-04 13:10 UTCEPSS rescore
  52. 2026-06-02 20:11 UTCEPSS rescore
  53. 2026-06-02 20:11 UTCEPSS rescore
  54. 2026-06-01 13:50 UTCEPSS rescore
  55. 2026-06-01 13:50 UTCEPSS rescore
  56. 2026-05-31 22:29 UTCEPSS rescore
  57. 2026-05-31 22:29 UTCEPSS rescore
  58. 2026-05-31 00:15 UTCEPSS rescore
  59. 2026-05-31 00:15 UTCEPSS rescore
  60. 2026-05-29 13:42 UTCEPSS rescore
  61. 2026-05-28 13:43 UTCEPSS rescore
  62. 2026-05-28 13:43 UTCEPSS rescore
  63. 2026-05-27 13:39 UTCEPSS rescore
  64. 2026-05-27 13:39 UTCEPSS rescore
  65. 2026-05-26 13:42 UTCEPSS rescore
  66. 2026-05-26 13:42 UTCEPSS rescore
  67. 2026-05-26 08:17 UTCEG score recompute
  68. 2026-05-26 08:17 UTCVendor advisory
  69. 2026-05-26 07:17 UTCEPSS rescore
  70. 2026-05-26 07:17 UTCEPSS rescore
  71. 2026-05-26 07:17 UTCEPSS rescore
  72. 2026-05-25 20:16 UTCOSV refresh

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCMoshe-ship/bidi-guard
    First seen Mar 21, 2026

    Scan code for invisible bidirectional Unicode characters (Trojan Source attack prevention, CVE-2021-42574)

    Open source ↗
  • GitHub PoCtin-z/solidity_CVE-2021-42574-POC
    First seen Jan 31, 2023

    POC of CVE-2021-42574 for solidity and solc compiler

    Open source ↗
  • GitHub PoCmaweil/bidi_char_detector
    First seen Nov 6, 2021

    Checks your files for existence of Unicode BIDI characters which can be misused for supply chain attacks. See CVE-2021-42574

    Open source ↗
  • GitHub PoCsimplylu/CVE-2021-42574
    First seen Nov 2, 2021

    Generate malicious files using recently published bidi-attack (CVE-2021-42574)

    Open source ↗

Frequently asked(5)

What is CVE-2021-42574?
CVE-2021-42574 is a high vulnerability published on November 1, 2021. 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…
When was CVE-2021-42574 disclosed?
CVE-2021-42574 was first published in the National Vulnerability Database on November 1, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-42574 actively exploited?
CVE-2021-42574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-42574?
CVE-2021-42574 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2021-42574?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-42574, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-42574

Explore →

Is Your Infrastructure Affected by CVE-2021-42574?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.