CVE-2021-40506

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-04-18. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

An issue was discovered in the ALU unit of the OR1200 (aka OpenRISC 1200) processor 2011-09-10 through 2015-11-11. The overflow flag is not being updated for the msb and mac instructions, which results in an incorrect value in the overflow flag. Any software that relies on this flag may experience corruption in execution.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 18, 2023

Last Modified

February 6, 2025

Advisory Details (2)

Auto-updated Oct 10, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

New vulnerabilities detected by our hardware fuzzer, TheHuzz

https://seth.engr.tamu.edu/software-releases/thehuzz/
GitHub commit

commit 2c0765d7ba12 (openrisc/or1200)

Fix landed in openrisc/or1200 commit 2c0765d7ba12 — awaiting tagged release

https://github.com/openrisc/or1200/commit/2c0765d7ba12813df273cd693a99c4e744f0fbd5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 213 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 04:18 UTCEG score recompute
  2. 2026-10-23 04:18 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-22 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-22 04:23 UTCEG score recompute
  5. 2026-10-22 04:23 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-21 16:28 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-21 04:27 UTCEG score recompute
  8. 2026-10-21 04:26 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-20 16:28 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-20 04:29 UTCEG score recompute
  11. 2026-10-20 04:29 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-19 04:33 UTCEG score recompute
  14. 2026-10-19 04:33 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-18 04:38 UTCEG score recompute
  16. 2026-10-18 04:37 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-17 04:14 UTCEG score recompute
  19. 2026-10-17 04:13 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-16 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-16 04:17 UTCEG score recompute
  22. 2026-10-16 04:17 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-15 02:18 UTCEG score recompute
  25. 2026-10-15 02:17 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 71 more
  1. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-13 22:59 UTCEG score recompute
  3. 2026-10-13 22:59 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-13 16:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-12 19:10 UTCGHSA enrichmentGHSA-9vj3-f442-h49r · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 19:10 UTCEG score recompute
  7. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-11 23:36 UTCEG score recompute
  9. 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-03 14:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-01 19:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-09-30 15:41 UTCEG score recompute
  21. 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-09-29 15:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-28 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-09-27 13:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-26 15:54 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  26. 2026-09-26 00:21 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  27. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  28. 2026-09-23 13:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  29. 2026-09-22 14:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-09-21 20:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  31. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  32. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  33. 2026-09-18 19:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  34. 2026-09-17 19:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  35. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  38. 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  39. 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-09-08 21:56 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-09-04 05:03 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-09-01 13:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-09-01 03:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-08-28 21:37 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  53. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  54. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  55. 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  56. 2026-08-23 00:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  57. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  59. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  60. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  61. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  62. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  64. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-11 13:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-08-08 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Frequently asked(5)

What is CVE-2021-40506?
CVE-2021-40506 is a critical-severity vulnerability; its CVE record was published on April 18, 2023. An issue was discovered in the ALU unit of the OR1200 (aka OpenRISC 1200) processor 2011-09-10 through 2015-11-11. The overflow flag is not being updated for the msb and mac instructions, which results in an incorrect value in the overflow flag. Any software that relies on this flag may experience…
When was the CVE record for CVE-2021-40506 published?
The CVE record for CVE-2021-40506 was published on April 18, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of February 6, 2025; the record at its source may have been updated since.
Is CVE-2021-40506 actively exploited?
CVE-2021-40506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-40506?
CVE-2021-40506 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2021-40506?
An upstream fix for CVE-2021-40506 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2021-40506?

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