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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

1 Apr 2026, 23:57 UTC

Last modified by the source

1 Apr 2026, 23:57 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-32wq-ppwg-3w4m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-32wq-ppwg-3w4m

Advisory: EnhancedLinq.Async is Vulnerable to Denial of Service via Transitive Dependency Microsoft.Bcl.Memory
IDs: GHSA-32wq-ppwg-3w4m
Record: https://patchnext.com/advisories/ghsa-32wq-ppwg-3w4m (revision 1, source checked 26 Oct 2026, 17:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: enhancedlinq.async 1.0.0-beta.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet enhancedlinq.async: affected >= 1.0.0-beta.1, < 1.0.0-beta.3; fixed in 1.0.0-beta.3

## Suggested inspection (read-only)
- NuGet enhancedlinq.async: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on enhancedlinq.async.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-32wq-ppwg-3w4m (GitHub-reviewed advisory GHSA-32wq-ppwg-3w4m lists affected ranges: NuGet enhancedlinq.async >=1.0.0-beta.1 <1.0.0-beta.3)

Commands are suggestions: review each one before running it.