Skip to content

[release/8.0-staging] Update MsQuic to 2.5.12 - #135883

Merged
ViveliDuCh merged 1 commit into
dotnet:release/8.0-stagingfrom
ViveliDuCh:msquic-2.5.12-release-8.0-staging
Oct 16, 2026
Merged

ViveliDuCh merged 1 commit into
dotnet:release/8.0-stagingfrom
ViveliDuCh:msquic-2.5.12-release-8.0-staging

Conversation

@ViveliDuCh

Copy link
Copy Markdown
Member

Fixes #135879

main PR #135749

Description

Updates the public release/8.0 servicing branch to use the publicly available MsQuic 2.5.12 package. This completes the private-to-public security servicing handoff so internal-to-public merges do not retain the private 2.5.11-ci.159417053 identifier that public CI cannot restore.

Customer Impact

Public release/8.0 builds fail restore with NU1603 because the private MsQuic servicing package is unavailable to public CI, blocking clean servicing builds.

Regression

This is not a product-code regression. The failure occurs during the post-disclosure dependency handoff from private MSRC bits to the corresponding public package.

Testing

Passed:

.\dotnet.cmd restore .\src\libraries\System.Net.Quic\src\System.Net.Quic.csproj /p:TargetOS=windows /p:TargetArchitecture=x64 --no-cache

The restore resolved MsQuic 2.5.12 without NU1603.

Risk

Low. This is a one-line patch-version dependency update to the public servicing package, with no managed-code changes. Full functional testing is delegated to CI.

Package authoring signed off?

IMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

No package project or package metadata is changed; this only updates the pinned native dependency version.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b0b9c360-7d5d-4fdc-bede-48036e9dd9b7
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

@ViveliDuCh

ViveliDuCh commented Oct 15, 2026 •

Copy link
Copy Markdown
Member Author

Approved via email

@ViveliDuCh ViveliDuCh added the Servicing-approved Approved for servicing release label Oct 15, 2026
@ViveliDuCh

Copy link
Copy Markdown
Member Author

/azp run runtime

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@ViveliDuCh
ViveliDuCh merged commit 4dd2b79 into dotnet:release/8.0-staging Oct 16, 2026
168 of 171 checks passed
ViveliDuCh added a commit that referenced this pull request Oct 16, 2026
…nternal-to-public builds (#135931)

#135883

The current internal-to-public merge against `release/8.0` is failing
across multiple Windows build legs because of the same warning-as-error:

src/libraries/System.Net.Quic/src/System.Net.Quic.csproj(0,0): error
NU1603: Warning As Error: System.Net.Quic depends on
Microsoft.Native.Quic.MsQuic.Schannel (>= 2.5.11-ci.159417053) but
Microsoft.Native.Quic.MsQuic.Schannel 2.5.11-ci.159417053 was not found.
An approximate best match of Microsoft.Native.Quic.MsQuic.Schannel
2.5.11-rc was resolved.

`2.5.11-ci.159417053` is the private MsQuic package used internally
during coordinated MSRC servicing, so it is intentionally unavailable to
public builds. Now that the corresponding public servicing package is
available as `2.5.12`,
[#135883](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fruntime%2Fpull%2F135884&data=05%7C02%7Cvivianad%40microsoft.com%7C98d3318ead20454faf1908df2aee27ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639276874519544099%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JIfQXtmjD%2FWBgKaNh5ZZXLClxdNNZQM0b5Z60o2MNjM%3D&reserved=0)
updates `release/8.0-staging` to that version. A targeted
`System.Net.Quic` restore passed locally without `NU1603`. Once this
change reaches `release/8.0` and the internal-to-public merge is
refreshed, public CI should be able to restore the dependency normally.
ViveliDuCh added a commit that referenced this pull request Oct 16, 2026
…nternal-to-public builds (#135931)

#135883

The current internal-to-public merge against `release/8.0` is failing
across multiple Windows build legs because of the same warning-as-error:

src/libraries/System.Net.Quic/src/System.Net.Quic.csproj(0,0): error
NU1603: Warning As Error: System.Net.Quic depends on
Microsoft.Native.Quic.MsQuic.Schannel (>= 2.5.11-ci.159417053) but
Microsoft.Native.Quic.MsQuic.Schannel 2.5.11-ci.159417053 was not found.
An approximate best match of Microsoft.Native.Quic.MsQuic.Schannel
2.5.11-rc was resolved.

`2.5.11-ci.159417053` is the private MsQuic package used internally
during coordinated MSRC servicing, so it is intentionally unavailable to
public builds. Now that the corresponding public servicing package is
available as `2.5.12`,
[#135883](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fruntime%2Fpull%2F135884&data=05%7C02%7Cvivianad%40microsoft.com%7C98d3318ead20454faf1908df2aee27ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639276874519544099%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JIfQXtmjD%2FWBgKaNh5ZZXLClxdNNZQM0b5Z60o2MNjM%3D&reserved=0)
updates `release/8.0-staging` to that version. A targeted
`System.Net.Quic` restore passed locally without `NU1603`. Once this
change reaches `release/8.0` and the internal-to-public merge is
refreshed, public CI should be able to restore the dependency normally.

(cherry picked from commit b60797b)
ViveliDuCh added a commit that referenced this pull request Oct 16, 2026
…nternal-to-public builds (#135931)

#135883

The current internal-to-public merge against `release/8.0` is failing
across multiple Windows build legs because of the same warning-as-error:

src/libraries/System.Net.Quic/src/System.Net.Quic.csproj(0,0): error
NU1603: Warning As Error: System.Net.Quic depends on
Microsoft.Native.Quic.MsQuic.Schannel (>= 2.5.11-ci.159417053) but
Microsoft.Native.Quic.MsQuic.Schannel 2.5.11-ci.159417053 was not found.
An approximate best match of Microsoft.Native.Quic.MsQuic.Schannel
2.5.11-rc was resolved.

`2.5.11-ci.159417053` is the private MsQuic package used internally
during coordinated MSRC servicing, so it is intentionally unavailable to
public builds. Now that the corresponding public servicing package is
available as `2.5.12`,
[#135883](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fruntime%2Fpull%2F135884&data=05%7C02%7Cvivianad%40microsoft.com%7C98d3318ead20454faf1908df2aee27ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639276874519544099%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JIfQXtmjD%2FWBgKaNh5ZZXLClxdNNZQM0b5Z60o2MNjM%3D&reserved=0)
updates `release/8.0-staging` to that version. A targeted
`System.Net.Quic` restore passed locally without `NU1603`. Once this
change reaches `release/8.0` and the internal-to-public merge is
refreshed, public CI should be able to restore the dependency normally.

(cherry picked from commit b60797b)
ViveliDuCh added a commit that referenced this pull request Oct 21, 2026
Fixes #136232 <!-- Issue Number -->

main PR #135749 <!-- Link to PR if any that fixed this in the main
branch. -->

# Description

<!-- Give a brief summary of the issue and how the pull request is
fixing it. -->

Update `MicrosoftNativeQuicMsQuicSchannelVersion` from 2.5.11 to 2.5.12,
applying the dependency change from #135883 to release/10.0. The
corresponding release/9.0 change is #135884.

The shared version property updates both the Windows product package and
functional-test package references. No audit suppressions or
managed-code changes are included.

# Customer Impact

<!-- What is the impact to customers of not taking this fix? -->

Public release/10.0 Windows builds fail restore with NU1902 because
Microsoft.Native.Quic.MsQuic.Schannel 2.5.11 is affected by
GHSA-2mxg-prvg-9jfg (CVE-2026-85790). Version 2.5.12 is the patched
release.

This removes the MsQuic blocker also seen in #136068, but does not
address the independent System.Security.Cryptography.Pkcs 9.0.6 audit
failures tracked in #136231.

# Regression

<!-- Is this fixing a problem that was introduced in the most recent
release, ie., fixing a regression? -->

An advisory against the existing native dependency causes NuGet audit
warnings to fail restore under the existing warnings-as-errors policy.
This is not a managed-code regression.

# Testing

<!-- What kind of testing has been done with the fix. -->

Commands were run on Windows x64 with the repository SDK 10.0.111:

- Before the change, `.\dotnet.cmd restore
.\src\libraries\System.Net.Quic\src\System.Net.Quic.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 --no-cache -v:quiet`
failed with NU1902 for Schannel 2.5.11.
- After the change, the same restore command passed (exit 0), and
project.assets.json resolved
Microsoft.Native.Quic.MsQuic.Schannel/2.5.12.
- `.\dotnet.cmd build
.\src\libraries\System.Net.Quic\src\System.Net.Quic.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 -v:quiet` passed with 0
warnings and 0 errors.
- `.\dotnet.cmd build /t:test
.\src\libraries\System.Net.Quic\tests\FunctionalTests\System.Net.Quic.Functional.Tests.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 -v:quiet` failed before
test execution: "The shared framework must be built before the local
targeting pack can be consumed." No functional tests ran.
- As a separate blocker check, `.\dotnet.cmd restore
.\src\tasks\Crossgen2Tasks\Crossgen2Tasks.csproj /p:TargetOS=windows
/p:TargetArchitecture=x64 --no-cache -v:quiet` failed with the existing
Pkcs 9.0.6 NU1902/NU1903 errors. The assets graph shows this dependency
comes from NuGet.Packaging/7.0.3-rc.46203.

A full main-branch baseline was explicitly waived for this
dependency-only change. No full runtime/libraries build or functional
test run was completed.

# Risk

<!-- Please assess the risk of taking this fix. Provide details backing
up your assessment. -->

Low: a one-line native dependency patch-version bump, matching the
version already used by main, release/8.0, and release/9.0. Targeted
restore and compilation passed; native runtime behavior remains
unverified locally because the functional tests could not start.

# Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet
package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older
versions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 792c8703-3703-4180-975a-9b86d809b48a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants