Skip to content

fix(security): move .NET to 10.0.13 for the October advisories - #214

Merged
mforce merged 1 commit into
mainfrom
fix/dotnet-10.0.13-security
Oct 20, 2026
Merged

mforce merged 1 commit into
mainfrom
fix/dotnet-10.0.13-security

Conversation

@mforce

@mforce mforce commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

Main is red. The scheduled audit (run 39248525834) fails on the October .NET 10.0.11 advisories, and so do #208, #210, #211, #212 and #213. Their failing runs list the same GHSAs. The Trivy runs also list CVEs in the 10.0.11 runtime and the base image's libssl3t64.

Changes

The other Microsoft.* packages stay at 10.0.11. #213 bumps them after a rebase.

Verification

  • dotnet list package --vulnerable --include-transitive: no vulnerable packages in any project.
  • Trivy on a local image build (os,library, HIGH and CRITICAL, --ignore-unfixed): 0 findings. Runtime is 10.0.13.
  • dotnet test tests/Collectify.Tests locally: 783 passed, 0 failed.
  • CI Server job: Collectify.Tests 783 of 783 passed, PostgresTests 15 of 15 passed. Image build and Trivy scan pass.

Bump System.Security.Cryptography.Xml 10.0.11 -> 10.0.13, which also pulls
Pkcs 10.0.13 (GHSA-r955-8q5j-3h83, GHSA-7hqp-7c5m-4vq6, GHSA-c399-9853-6jmj,
GHSA-846f-f764-76mx, GHSA-2fmv-rv2c-59x7). Re-pin the node, sdk and aspnet
base images to the current digests, which ship the 10.0.13 runtime
(CVE-2026-70188, CVE-2026-70175, CVE-2026-58280) and the patched libssl3t64
(CVE-2026-84782).
@mforce
mforce merged commit a72498f into main Oct 20, 2026
10 checks passed
@mforce
mforce deleted the fix/dotnet-10.0.13-security branch October 20, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant