CVE Intelligence
High Injection

CVE-2021-24112 — .NET Core Remote Code Execution Vulnerability

.NET Core Remote Code Execution Vulnerability

Published Feb 25, 2021 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 3.5% (30-day exploitation probability)+13
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

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.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
3.45%
ahead of 89% of scored CVEs · Oct 14, 2026
Affects
Microsoft
.net and 8 more
CVSS base
8.1
High · 3 source(s)
Prioritization reference: 9.8 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft .net, Microsoft .NET 5.0, Microsoft .net Core…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft .net ≥ 5.0 and ≤ 5.0.2 Vulnerable NIST National Vulnerability Database
Microsoft .NET 5.0 ≥ 5.0.0 and < publication Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft .net Core ≥ 2.1 and ≤ 2.1.24≥ 3.1 and ≤ 3.1.11 Vulnerable NIST National Vulnerability Database
Microsoft .NET Core 2.1 ≥ 2.1 and < publication Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft .NET Core 3.1 ≥ 3.1 and < publication Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Mono ≥ 6.12.0 and < 6.12.0.122 Vulnerable NIST National Vulnerability Database
Microsoft Mono 6.12.0 ≥ 6.12.0 and < publication Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Visual Studio 2019 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Visual Studio 2019 for Mac ≥ 8.0.0 and < publication Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

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

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.1 CVSS 3.1 High 2.2 5.9 secure@microsoft.com via NIST National Vulnerability Database
8.1 CVSS 3.1 High — — microsoft via CVE Program (cve.org) e CISA ADP
7.5 CVSS 2.0 High 10.0 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: secure@microsoft.com)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.45%

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).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · microsoft/visual studio 2019 for mac, microsoft/mono 6.12.0, microsoft/.net core 2.1, microsoft/.net core 3.1, microsoft
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2021
  • CVE published
    Feb 25, 2021 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
Injection
same class
CWE-94
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-58649 .NET Information Disclosure Vulnerability Sep 8, 2026
  • High CVE-2026-70354 Out-of-bounds Write in Microsoft Visual Studio 2022 Aug 11, 2026
  • Medium CVE-2026-62899 HTTP Request Smuggling in Microsoft Visual Studio 2022 Aug 11, 2026
  • Medium CVE-2026-62900 Improper removal of sensitive information before storage or transfer in .NET allows an… Aug 11, 2026
  • Medium CVE-2026-62902 Inclusion of functionality from untrusted control sphere in .NET allows an unauthorized… Aug 11, 2026
  • High CVE-2026-62909 Unchecked Return Value in Microsoft Visual Studio 2022 Aug 11, 2026

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 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-2021-24112 is ".NET Core Remote Code Execution Vulnerability", rated High. It affects .net (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 3.45% 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.