Skip to content

Dependencies: Pin SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version (closes #23325) - #23393

Merged
AndyButland merged 1 commit into
release/17.6from
v17/security/23325-pin-sqlite-version
Jul 16, 2026
Merged

Dependencies: Pin SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version (closes #23325)#23393
AndyButland merged 1 commit into
release/17.6from
v17/security/23325-pin-sqlite-version

Conversation

@AndyButland

@AndyButland AndyButland commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Description

SQLitePCLRaw.lib.e_sqlite3 was resolving to the vulnerable 2.1.11 (GHSA-2m69-gcr7-jv3q, high severity). It is a purely transitive dependency, reached via Microsoft.Data.Sqlite (used by Umbraco.Cms.Persistence.Sqlite) and Microsoft.EntityFrameworkCore.Sqlite (used by the EF Core persistence projects), both of which pull it in through SQLitePCLRaw.bundle_e_sqlite3.

SQLitePCLRaw.lib.e_sqlite3 has been patched in 2.1.12 and we've run all Umbraco integration tests on this version, which pass (as CI on this PR should confirm).

I was waiting a few days for our direct dependencies to pin their versions on 2.1.12. However as yet they haven't. The latest available versions of those direct dependencies (Microsoft.Data.Sqlite / Microsoft.EntityFrameworkCore.Sqlite 10.0.10), released two days ago, still reference bundle_e_sqlite3 2.1.11, so there is no upstream floor bump to adopt yet.

As such, I think we'll need to pin Umbraco instead so we ship referencing a non-vulnerable version and avioid the build warnings.

This pins the transitive SQLitePCLRaw.lib.e_sqlite3 forward to the patched 2.1.12 in Directory.Packages.props, following the existing convention for transitive pinned versions. Only the native lib.e_sqlite3 package is flagged, so it is the sole package pinned.

Fixes #23325.

Testing

Solution should build and CI checks pass.

Copilot AI review requested due to automatic review settings July 16, 2026 04:59
@claude

claude Bot commented Jul 16, 2026

Copy link
Copy Markdown

Claude finished @AndyButland's task in 1m 32s —— View job


PR Review

Target: origin/release/17.6 · Based on commit: beec659 · Classified as: Config-only

Pins the transitive SQLitePCLRaw.lib.e_sqlite3 from vulnerable 2.1.11 to patched 2.1.12 to address GHSA-2m69-gcr7-jv3q (high severity).


No issues found. The change:

  • Is correctly placed in the existing "Transitive pinned versions" <ItemGroup> alongside the Microsoft.OpenApi and other prior security pins
  • Follows the established comment convention (explains the CVE, the packages pulling it in, and the exit condition)
  • Will take effect automatically since CentralPackageTransitivePinningEnabled is true in the file

Approved

This looks good to be merged as-is, but please do a manual sanity check and testing before merging.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Pins the transitive NuGet dependency SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version via Central Package Management, preventing resolution to the vulnerable 2.1.11 while upstream packages still reference bundle_e_sqlite3 2.1.11.

Changes:

  • Adds a transitive pin for SQLitePCLRaw.lib.e_sqlite3 to 2.1.12 in Directory.Packages.props.
  • Documents the rationale and advisory reference inline alongside other transitive pins.

@claude claude Bot added the area/backend label Jul 16, 2026
@sonarqubecloud

Copy link
Copy Markdown

@AndyButland
AndyButland enabled auto-merge (squash) July 16, 2026 06:22
@AndyButland
AndyButland merged commit 04075f3 into release/17.6 Jul 16, 2026
30 checks passed
@AndyButland
AndyButland deleted the v17/security/23325-pin-sqlite-version branch July 16, 2026 06:35
AndyButland added a commit that referenced this pull request Jul 16, 2026
…ion (closes #23325) (#23393)

Pin SQLitePCLRaw.lib.e_sqlite3 to a non-vulnerable version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants