How severe is CVE-2026-62901?

No CVSS score has been assigned to CVE-2026-62901 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-62901?

CVE-2026-62901 affects the following packages: dotnet (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-62901?

Update dotnet to 8.0.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62901 is resolved across your whole dependency graph.

How do I detect CVE-2026-62901 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dotnet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-62901 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-62901?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-62901 can be triaged on real exposure rather than presence alone.

Is CVE-2026-62901 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-62901 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-62901?

CVE-2026-62901 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-62901?

CVE-2026-62901 is classified as CWE-606 (CWE-606). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-62901 published, and has it been updated?

CVE-2026-62901 was published on August 17, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2026-62901 — dotnet

CVE-2026-62901 is a CWE-606 vulnerability in dotnet. A fix is available for dotnet — see the affected versions and patch details below.

.NET Denial of Service Vulnerability

Also known asBIT-dotnet-sdk-2026-62901GHSA-m93f-wj8c-rp8p

Published

Aug 17, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-62901.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

📦dotnet

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

Unchecked input for loop condition in .NET allows an unauthorized attacker to deny service over a network.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`dotnet`	≥ 8.0.0&&< 8.0.30	8.0.30

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dotnet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dotnet to 8.0.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62901 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-62901 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-62901. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability in System.Net.WebSockets is rated as Important. An unauthenticated attacker could exploit this flaw to cause a denial of service in affected .NET applications, impacting service availability and reliability. This affects Red Hat products utilizing .NET 6.0 and newer versions.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-62901 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`dotnet8.0-0:8.0.130-1.el10_2`	RHSA-2026:54541
Red Hat Enterprise Linux 10	`dotnet9.0-0:9.0.120-1.el10_2`	RHSA-2026:54590
Red Hat Enterprise Linux 10	`dotnet10.0-0:10.0.111-1.el10_2`	RHSA-2026:55858
Red Hat Enterprise Linux 10.0 Extended Update Support	`dotnet8.0-0:8.0.130-1.el10_0`	RHSA-2026:58566
Red Hat Enterprise Linux 10.0 Extended Update Support	`dotnet9.0-0:9.0.120-1.el10_0`	RHSA-2026:58567
Red Hat Enterprise Linux 8	`dotnet8.0-0:8.0.130-1.el8_10`	RHSA-2026:54538
Red Hat Enterprise Linux 8	`dotnet10.0-0:10.0.111-1.el8_10`	RHSA-2026:54542
Red Hat Enterprise Linux 8	`dotnet9.0-0:9.0.120-1.el8_10`	RHSA-2026:54550

UbuntuHIGH

USN-8641-1Ubuntu

Frequently Asked Questions

Unchecked input for loop condition in .NET allows an unauthorized attacker to deny service over a network.

O3 Security · Impact-Aware SCA

Is CVE-2026-62901 in your dependencies?

O3 Security finds CVE-2026-62901 across Bitnami dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works