Fix: pin Microsoft.Bcl.Memory to 10.0.4 (CVE-2026-26127) - #261
Merged
dbezic (dbezic) merged 2 commits intoJul 7, 2026
Conversation
Patches High-severity DoS (GHSA-73j8-2gch-69rq) in transitive Microsoft.Bcl.Memory <= 10.0.3, pulled in via Microsoft.Agents.Connector.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses a high-severity DoS vulnerability (CVE-2026-26127 / GHSA-73j8-2gch-69rq) by centrally pinning the transitive dependency Microsoft.Bcl.Memory to a patched version, aligning with the repo’s Central Package Management + transitive pinning approach.
Changes:
- Add a central transitive pin for
Microsoft.Bcl.Memoryto version10.0.4. - Document the security motivation for the pin directly alongside the package version entry.
Beka Arevadze (BekaAre)
previously approved these changes
Jul 7, 2026
…ts.* to >= 1.6.150
Beka Arevadze (BekaAre)
approved these changes
Jul 7, 2026
dbezic (dbezic)
deleted the
user/dominikbezic/fix-bcl-memory-cve-2026-26127
branch
July 7, 2026 10:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Patch High-severity DoS in transitive
Microsoft.Bcl.Memory(CVE-2026-26127)Summary
Component Governance flagged a High severity vulnerability in the transitive
dependency
Microsoft.Bcl.Memory10.0.2. This PR pins the package to thepatched version 10.0.4 to remediate the alert.
Vulnerability
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)Microsoft.Bcl.Memory >= 10.0.0, <= 10.0.3(repo resolved 10.0.2)How it entered the repo
The package is not a direct dependency — it is pulled in transitively via the
Microsoft Agents SDK, which is why
dotnet package update Microsoft.Bcl.Memorydoes not work:
Fix
The repo uses Central Package Management with
CentralPackageTransitivePinningEnabled=true, so a singlePackageVersionentry in
src/Directory.Packages.propspins the transitive dependency to thepatched version across all projects:
10.0.4also aligns with the other10.0.4BCL /Microsoft.Extensions.*packages already pinned in the file.
Verification
Microsoft.Bcl.Memorynow resolves to 10.0.4 across all projects(
dotnet list package --include-transitive).dotnet list package --vulnerable --include-transitivereports novulnerable packages.
dotnet build src/Microsoft.Agents.A365.Sdk.slnsucceeds with 0 warnings, 0 errors.Files changed
src/Directory.Packages.props— added transitive pin forMicrosoft.Bcl.Memory10.0.4.