Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

CVSS 3.1 5.5 MEDIUMEUVD CVSS 3.1 5.5 CVSS 3.1 · [email protected] · Secondary 5.5 MEDIUMCVSS 3.1 · [email protected] · Secondary 5.5 MEDIUMCVSS 2.0 · [email protected] · Primary 2.1 LOWCVSS_V3 Publisher rating MODERATEFixed by Microsoft.AspNetCore.Authentication.JwtBearer 2.1.29Fixed by Microsoft.AspNetCore.Authentication.JwtBearer 3.1.18Fixed by Microsoft.AspNetCore.Authentication.JwtBearer 5.0.9KEV status unknown

cve-program · CVE-2021-34532

Published

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

euvd · EUVD-2021-1835

Published

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

nvd · CVE-2021-34532

Published

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

Read the publisher's advisory

osv · GHSA-q7cg-43mg-qp69

Published

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. An information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed. ### Patches * If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0. * If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1. * If you're using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1. * If your application is using .NET Core 2.1 running on .NET Framework see the [Updating .NET Core 2.1 on .NET Framework](#updating-2.1) section below. ### <a name="updating-2.1"></a> Updating .NET Core 2.1 on .NET Framework If you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly. #### Direct dependencies Direct dependencies are discoverable by examining your `csproj` file. They can be fixed by [editing the project file](#fixing-direct-dependencies) or using NuGet to update the dependency. #### Transitive dependencies Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package `Contoso.Utility` which, in turn, depends on `Contoso.Internals` and you add the `Contoso.Utility` package to your project now your project has a direct dependency on `Contoso.Utility` and, because `Contoso.Utility` depends 'Contoso.Internals', your application gains a transitive dependency on the `Contoso.Internals` package. Transitive dependencies are reviewable in two ways: * In the Visual Studio Solution Explorer window, which supports searching. * By examining the `project.assets.json` file contained in the obj directory of your project for `csproj` based projects The `project.assets.json` files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies. There are two ways to view transitive dependencies. You can either [use Visual Studio’s Solution Explorer](#vs-solution-explorer), or you can review [the `project.assets.json` file](#project-assets-json)). ##### <a name="vs-solution-explorer"></a>Using Visual Studio Solution Explorer To use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the [vulnerable package](#affected-software) and make a note of the version numbers of any results you find. For example, search for `Microsoft.AspNetCore.Authentication.JwtBearer` and update the package to the latest version ##### <a name="project-assets-json"></a> Manually reviewing project.assets.json Open the *project.assets.json* file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file. Visual Studio and Visual Studio Code provide JSON friendly editing. Search the *project.assets.json* file for the [vulnerable package](#affected-software), using the format `packagename/` for each of the package names from the preceding table. If you find the assembly name in your search: * Examine the line on which they are found, the version number is after the `/`. * Compare to the [vulnerable versions table](#affected-software). For example, a search result that shows `Microsoft.AspNetCore.Authentication.JwtBearer/2.1.0` is a reference to version 2.1.1 of `Microsoft.AspNetCore.Authentication.JwtBearer`. If your *project.assets.json* file includes references to the [vulnerable package](#affected-software), then you need to fix the transitive dependencies. If you have not found any reference to any vulnerable packages, this means either * None of your direct dependencies depend on any vulnerable packages, or * You have already fixed the problem by updating the direct dependencies. #### Other Details - Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/195 - An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/35246 - MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-34532

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2021-34532

This is a saved version of the risk data. The advisory details have their own history. Latest risk data.

No CISA KEV listing is included in this saved record. Exploitation may still have occurred.

FIRST EPSS: 1.22 % · percentile 68.66 % · scored 31 Oct 2026. This score is more than two days old.

Saved 01 Nov 2026 03:04:52 UTC · View this risk record (JSON)

Advisory history

19 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

22 Nov 2026 02:47:29 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

20 Nov 2026 01:40:50 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

18 Nov 2026 00:39:47 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

16 Nov 2026 00:12:50 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

14 Nov 2026 00:02:54 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

11 Nov 2026 23:04:08 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

9 Nov 2026 22:13:30 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

7 Nov 2026 21:01:20 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

5 Nov 2026 20:48:14 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

3 Nov 2026 21:57:44 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

nvd · CVE-2021-34532 · Published

3 Nov 2026 20:05:46 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

2 Nov 2026 19:57:16 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

cve-program · CVE-2021-34532 · Published

1 Nov 2026 19:08:31 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

30 Oct 2026 18:51:08 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

28 Oct 2026 15:52:51 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

24 Oct 2026 19:22:10 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

euvd · EUVD-2021-1835 · Published

24 Oct 2026 18:17:33 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

nvd · CVE-2021-34532 · Published

23 Oct 2026 15:48:27 UTC

ASP.NET Core and Visual Studio Information Disclosure Vulnerability

cve-program · CVE-2021-34532 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 08:05 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current