VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

dotnet-sdk: vulnerability history, versions and safety

dotnet-sdk is a package in the Bitnami ecosystem. Vulert records 133 vulnerabilities for it across 49 affected ranges, from Nov 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
133 vulnerabilities recorded C6 H104 M23
i
1 with no fix published

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

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

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dotnet-sdk vulnerabilities

Vulert verdict on dotnet-sdk i

Updated on 23 Oct 2026

Careful: one of the 133 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 133 over 2 years · 58 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 10.0.0 up to 10.0.13 (exclusive) 1
from 10.0.0 up to 10.0.4 (exclusive) 1
from 9.0.0 up to 9.0.100 (exclusive) 1
from 9.0.0 up to 9.0.20 (exclusive) 1
from 9.0.0 up to 9.0.14 (exclusive) 1
from 9.0.0 up to 9.0.1 (exclusive) 2
from 8.0.0 up to 8.0.101 (exclusive) 5
from 8.0.0 up to 8.0.31 (exclusive) 3
from 8.0.0 up to 8.0.30 (exclusive) 11
from 8.0.0 up to 8.0.29 (exclusive) 17
from 8.0.0 up to 8.0.28 (exclusive) 3
from 8.0.0 up to 8.0.27 (exclusive) 4
from 8.0.0 up to 8.0.26 (exclusive) 4
from 8.0.0 up to 8.0.24 (exclusive) 1
from 8.0.0 up to 8.0.22 (exclusive) 1
from 8.0.0 up to 8.0.21 (exclusive) 2
from 8.0.0 up to 8.0.10 (exclusive) 1
from 8.0.0 up to 8.0.8 (exclusive) 3
from 8.0.0 up to 8.0.7 (exclusive) 2
from 8.0.0 up to 8.0.5 (exclusive) 4
up to 8.0.0 (exclusive) 1
from 7.0.0 up to 7.0.19 (exclusive) 2
from 7.0.0 up to 7.0.17 (exclusive) 2
from 7.0.0 up to 7.0.13 (exclusive) 1
from 7.0.0 up to 7.0.12 (exclusive) 1
from 7.0.0 up to 7.0.7 (exclusive) 1
from 6.0.0 up to 6.0.418 (exclusive) 2
from 6.0.0 up to 6.0.36 (exclusive) 2
from 6.0.0 up to 6.0.35 (exclusive) 3
from 6.0.0 up to 6.0.32 (exclusive) 1
from 6.0.0 up to 6.0.29 (exclusive) 1
from 6.0.0 up to 6.0.26 (exclusive) 4
from 6.0.0 up to 6.0.25 (exclusive) 2
from 6.0.0 up to 6.0.23 (exclusive) 1
from 6.0.0 up to 6.0.21 (exclusive) 3
from 6.0.0 up to 6.0.20 (exclusive) 2
from 6.0.0 up to 6.0.18 (exclusive) 3
from 6.0.0 up to 6.0.16 (exclusive) 1
from 6.0.0 up to 6.0.8 (exclusive) 1
from 6.0.0 up to 6.0.1 (exclusive) 15
from 5.0.0 up to 5.0.15 (exclusive) 2
from 5.0.0 up to 5.0.14 (exclusive) 1
from 5.0.0 up to 5.0.9 (exclusive) 2
from 5.0.0 up to 5.0.7 (exclusive) 1
from 5.0.0 up to 5.0.6 (exclusive) 1
from 5.0.0 up to 5.0.4 (exclusive) 1
from 5.0.0 up to 5.0.3 (exclusive) 2
from 5.0.0 up to 5.0.1 (exclusive) 5
from 5.0-preview1.0 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 68
  • 2025 8
  • 2026 56

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

03 Vulnerabilities

Recorded vulnerabilities for dotnet-sdk

The 5 most severe of 133 vulnerabilities recorded for this package

Search all 133 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-43483: .NET SDK Denial of Service Vulnerability N/A high 6.0.35 22 Oct 2024
CVE-2026-96222: dotnet-sdk Active Directory Federation Services Spoofing Vulnerability N/A high 8.0.5 21 Oct 2026
CVE-2026-32178: .NET Spoofing Vulnerability in dotnet-sdk Package N/A high 8.0.26 08 May 2026
CVE-2025-55247: .NET Elevation of Privilege Vulnerability in dotnet-sdk N/A high 8.0.21 24 Oct 2025
CVE-2026-42899: dotnet-sdk ASP.NET Core Denial of Service Vulnerability N/A high 8.0.27 14 May 2026

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 dotnet-sdk

Is dotnet-sdk safe to use?

Vulert records 133 vulnerabilities for dotnet-sdk in Bitnami: 6 critical, 104 high, 23 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does dotnet-sdk have?

133 vulnerabilities are recorded for dotnet-sdk in the Bitnami ecosystem: 6 critical, 104 high, 23 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dotnet-sdk vulnerabilities disclosed?

58 vulnerabilities were recorded for dotnet-sdk in the last 12 months, and the oldest entry in this database dates to 21 Nov 2023. 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 dotnet-sdk 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 dotnet-sdk for upcoming vulnerabilities?

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