Update package versions and mitigate CVE-2025-6965 (transitive SQLite)#605
Merged
Conversation
Bump central package versions in Directory.Packages.props: - Microsoft.WindowsAppSDK 1.7.250909003 -> 2.2.0 - Microsoft.Extensions.* 10.0.5 -> 10.0.9 - System.CommandLine 2.0.5 -> 2.0.9 - Microsoft.Data.Sqlite / Microsoft.EntityFrameworkCore.Sqlite 10.0.5 -> 10.0.9 - Microsoft.NET.Test.Sdk 18.4.0 -> 18.6.0 - coverlet.collector 8.0.1 -> 10.0.1 Add a temporary security override pinning the transitively-resolved native SQLitePCLRaw.lib.e_sqlite3 to 3.50.3 (SQLite 3.50.3) to clear CVE-2025-6965 (GHSA-2m69-gcr7-jv3q). Microsoft.Data.Sqlite / EF Core 10.0.9 still pull SQLitePCLRaw.bundle_e_sqlite3 2.1.11 -> lib.e_sqlite3 2.1.11; lib.e_sqlite3 3.50.3 is native-only so the SQLitePCLRaw 2.x managed core is unchanged. Enabled CentralPackageTransitivePinningEnabled to allow the pin. Tracked for removal by #604. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ryanriesMSFT
approved these changes
Jun 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates centrally-managed NuGet package versions and adds a Central Package Management transitive pin to mitigate CVE-2025-6965 by overriding the resolved native SQLite binary version.
Changes:
- Bumped centrally-managed package versions (WindowsAppSDK, Extensions.*, System.CommandLine, Sqlite/EFCore.Sqlite, and test tooling).
- Enabled Central Package transitive pinning and pinned
SQLitePCLRaw.lib.e_sqlite3to3.50.3as a temporary security override for CVE-2025-6965 (tracked by #604).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
Updates centrally-managed package versions in
Directory.Packages.propsand adds a temporarysecurity override to clear the CVE-2025-6965 advisory on the transitive native SQLite library.
Package version bumps
SQLite CVE-2025-6965 mitigation
Microsoft.Data.Sqlite/Microsoft.EntityFrameworkCore.Sqlite10.0.9 still transitively resolveSQLitePCLRaw.bundle_e_sqlite32.1.11 →SQLitePCLRaw.lib.e_sqlite32.1.11 (SQLite < 3.50.2), which isflagged by CVE-2025-6965 / GHSA-2m69-gcr7-jv3q
(High). There is no 2.1.x patch.
This pins only the native
SQLitePCLRaw.lib.e_sqlite3to3.50.3via Central Package Managementtransitive pinning (
CentralPackageTransitivePinningEnabled). That package has no managed dependencies,so the SQLitePCLRaw 2.x managed core (which
Microsoft.Data.Sqlite10.0.9 was built against) isunchanged — only the bundled SQLite native binary moves to 3.50.3.
Temporary workaround until
Microsoft.Data.Sqliteships the upstream fix(dotnet/efcore #38402, milestone 11.0-preview6).
Removal is tracked by #604.
Verification
dotnet nuget whyon all three SQLite-consuming projects (Runtime,Provider.Database,Eventing.TestUtils) now resolveslib.e_sqlite3→ 3.50.3 (bundle stays 2.1.11).dotnet restoreon those projects: no NuGet version-conflict warnings.EventLogExpert.Provider.Databasebuilds clean (0 warnings, 0 errors).