.NET Releases

.NET 2.1.30 released with fixes for 3 CVEs

.NET 2.1.30 was released on 2021-08-19. It ships .NET Runtime 2.1.30, ASP.NET Core Runtime 2.1.30, SDK 2.1.818, 2.1.526. The official release metadata lists 3 CVEs addressed in this release. .NET 2.1 has reached end of support (2021-08-21) and no longer receives fixes.

What was released From the source

According to Microsoft's official .NET release metadata, .NET 2.1.30 was published on 2021-08-19. The components and versions in this release are:

  • Release: .NET 2.1.30
  • Release date: 2021-08-19
  • .NET Runtime: 2.1.30
  • ASP.NET Core Runtime: 2.1.30
  • SDK versions: 2.1.818, 2.1.526
  • C# language version: 7.3
  • Release type: LTS
  • Support phase: End of life
  • End of support: 2021-08-21
  • Security release: Yes (3 CVEs listed)

At a glance · .NET release

LTSEnd of life2.1.30

Security fixes listed for this release From the source

The release metadata marks this as a security release and lists the following CVE identifiers. Severity, affected components and mitigations for each CVE are described in the official release notes and the CVE records.

  • CVE-2021-26423
  • CVE-2021-34485
  • CVE-2021-34532

Why it matters Analysis

Applications that run on an earlier .NET 2.1 patch remain exposed to the issues fixed in this release until they are updated. Framework-dependent apps are fixed by updating the runtime on the host or in the container image; self-contained and single-file apps embed the runtime and must be rebuilt and redeployed.

.NET 2.1 is out of support since 2021-08-21: Microsoft no longer ships security fixes for it. Applications still on this version should move to a supported .NET release.

Who should care Analysis

  • Teams running .NET 2.1 applications in production or testing
  • Owners of container images built on .NET 2.1 base images
  • Teams that publish self-contained or single-file applications
  • Developers and CI pipelines that pin an SDK version in global.json

How to update Analysis

  1. Check installed versions with dotnet --list-runtimes and dotnet --list-sdks.
  2. Plan an upgrade to a supported .NET version; the official download page lists the versions that are still in support.
  3. Update target frameworks, rebuild, and run your test suite before moving production to the new version.

Sources and further reading

Original: “.NET 2.1.30 released with 3 security fixes”, .NET release metadata, published 19 Aug 2021, retrieved 16 Oct 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.