GHSA-32WQ-PPWG-3W4M

GHSA-32WQ-PPWG-3W4M is a high-severity security vulnerability in EnhancedLinq.Async (nuget), affecting versions >= 1.0.0-beta.1, < 1.0.0-beta.3. It is fixed in 1.0.0-beta.3.

Summary

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.

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.

GHSA-32WQ-PPWG-3W4M has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.0-beta.3); upgrading removes the vulnerable code path.

Affected versions

EnhancedLinq.Async (>= 1.0.0-beta.1, < 1.0.0-beta.3)

Security releases

EnhancedLinq.Async → 1.0.0-beta.3 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

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.

Frequently Asked Questions

  1. What is GHSA-32WQ-PPWG-3W4M? GHSA-32WQ-PPWG-3W4M is a high-severity security vulnerability in EnhancedLinq.Async (nuget), affecting versions >= 1.0.0-beta.1, < 1.0.0-beta.3. It is fixed in 1.0.0-beta.3.
  2. How severe is GHSA-32WQ-PPWG-3W4M? GHSA-32WQ-PPWG-3W4M has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of EnhancedLinq.Async are affected by GHSA-32WQ-PPWG-3W4M? EnhancedLinq.Async (nuget) versions >= 1.0.0-beta.1, < 1.0.0-beta.3 is affected.
  4. Is there a fix for GHSA-32WQ-PPWG-3W4M? Yes. GHSA-32WQ-PPWG-3W4M is fixed in 1.0.0-beta.3. Upgrade to this version or later.
  5. Is GHSA-32WQ-PPWG-3W4M exploitable, and should I be worried? Whether GHSA-32WQ-PPWG-3W4M is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-32WQ-PPWG-3W4M is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-32WQ-PPWG-3W4M? Upgrade EnhancedLinq.Async to 1.0.0-beta.3 or later.

Other vulnerabilities in EnhancedLinq.Async

Stop the waste.
Protect your environment with Kodem.