VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

dotnet6: vulnerability history, versions and safety

dotnet6 is a package in the Ubuntu ecosystem. Vulert records 46 vulnerabilities for it across 21 releases, from Sep 2022 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
46 vulnerabilities recorded U46
i
7 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dotnet6 vulnerabilities

Vulert verdict on dotnet6 i

Updated on 23 Oct 2026

Careful: 7 of the 46 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 46 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 7 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 46 over 2 years · 0 in the last year i
  • Latest disclosure 13 May 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 7 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for dotnet6, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 21 of 21 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 24
  • 2024 12
  • 2025 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 46 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for dotnet6

The 5 most severe of 46 vulnerabilities recorded for this package

Search all 46 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Elevation of Privilege Vulnerability in .NET Packages: CVE-2023-36049 9.8 critical 6.0.125-0ubuntu1~22.04.1 14 Nov 2023
Critical Security Feature Bypass in .NET Packages: CVE-2024-0057 9.8 critical 6.0.126-0ubuntu1~22.04.1 09 Jan 2024
Critical Remote Code Execution Vulnerability in .NET Packages: CVE-2025-21176 8.8 high No fix published 15 Jan 2025
ASP.NET and Visual Studio Security Feature Bypass Vulnerability in dotnet6 and dotnet7 Packages 8.1 high 6.0.120-0ubuntu1~22.04.1 11 Jul 2023
Critical Vulnerability in .NET Packages: External Control of File Name or Path 8.0 high No fix published 13 May 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dotnet6

Is dotnet6 safe to use?

Vulert records 46 vulnerabilities for dotnet6 in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 46 not yet rated. 7 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does dotnet6 have?

46 vulnerabilities are recorded for dotnet6 in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 46 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dotnet6 vulnerabilities disclosed?

0 vulnerabilities were recorded for dotnet6 in the last 12 months, and the oldest entry in this database dates to 13 Sep 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of dotnet6 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor dotnet6 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dotnet6 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.