Skip to content

EnhancedLinq.Async is Vulnerable to Denial of Service via Transitive Dependency Microsoft.Bcl.Memory

High severity GitHub Reviewed Published Mar 31, 2026 in alastairlundy/EnhancedLinq

Package

nuget EnhancedLinq.Async (NuGet)

Affected versions

>= 1.0.0-beta.1, < 1.0.0-beta.3

Patched versions

1.0.0-beta.3

Description

Impact

Microsoft.Bcl.Memory, a transitive dependency of EnhancedLinq.Async, had a Denial of Service security vulnerability, CVE-2026-26127, thus affecting EnhancedLinq.Async versions that had vulnerable versions of Microsoft.Bcl.Memory as a transitive dependency.

Patches

EnhancedLinq.Async 1.0.0 Beta 3 updates the dependency on System.Linq.AsyncEnumerable to version 10.0.4 or newer which in turn updates the transitive dependency on Microsoft.Bcl.Memory from version 10.0.3 to 10.0.4 or newer, resolving the vulnerability.

Workarounds

No workarounds exist for this vulnerability.

How to fix the issue

To update the EnhancedLinq.Async NuGet package, use one of the following methods:

NuGet Package Manager UI in Visual Studio:

  • Open the project in Visual Studio.
  • Right-click on the project in Solution Explorer and select "Manage NuGet Packages..." or navigate to "Project > Manage NuGet Packages".
  • In the NuGet Package Manager window, select the "Updates" tab. This tab lists packages with available updates from configured package sources.
  • Select the package(s) to update. A specific version can be chosen from the dropdown, or the latest available version can be selected.
  • Click the "Update" button.

Using the NuGet Package Manager Console in Visual Studio:

  • Open the project in Visual Studio.
  • Navigate to "Tools > NuGet Package Manager > Package Manager Console".
  • To update a specific package to its latest version, use the following Update-Package command:
Update-Package -Id EnhancedLinq.Async

Using the .NET CLI (Command Line Interface):

  • Open a terminal or command prompt in the project's directory.
  • To update a specific package to its latest version, use the following add package command:
dotnet package update EnhancedLinq.Async

Once the NuGet package reference has been updated, the application must be recompiled and redeployed.

References

Published to the GitHub Advisory Database Apr 1, 2026
Reviewed Apr 1, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Weaknesses

Improper Validation of Array Index

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. Learn more on MITRE.

Dependency on Vulnerable Third-Party Component

The product has a dependency on a third-party component that contains one or more known vulnerabilities. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-32wq-ppwg-3w4m
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.