Skip to content

chore: pin SQLitePCLRaw 2.1.14 in the test project for CVE-2025-6965 (5.x) - #204

Open
CaffeinatedCoder wants to merge 1 commit into
release/5.xfrom
chore/202-sqlite-cve-5.x
Open

CaffeinatedCoder wants to merge 1 commit into
release/5.xfrom
chore/202-sqlite-cve-5.x

Conversation

@CaffeinatedCoder

Copy link
Copy Markdown
Owner

Closes #202

Cherry-pick (-x) of #203 from main. release/5.x has the same test-project reference.

Problem

The test project pins Microsoft.EntityFrameworkCore.Sqlite at the 10.0.0 floor, which brings SQLitePCLRaw 2.1.11 and with it SQLite 3.49.1, vulnerable to CVE-2025-6965 (GHSA-2m69-gcr7-jv3q). Dependabot reports only on the default branch, so this branch has no alert of its own. No package under src/ references SQLite, so consumers are not affected.

Change

The same three files as #203, applied cleanly:

  • the test project references SQLitePCLRaw.bundle_e_sqlite3 2.1.14 directly. EF Core and Microsoft.Data.Sqlite stay at 10.0.0.
  • test/Directory.Build.targets removes the pin under EfFloat, so a floated patch with a later SQLitePCLRaw cannot fail the restore with NU1605.
  • .github/dependabot.yml ignores SQLitePCLRaw majors.

Tests

#202 is already closed by #203. Closes #202 is here for the hygiene check and has no effect on a release branch.

🤖 Generated with Claude Code

EF Core Sqlite 10.0.0, the floor the test project pins, brings
SQLitePCLRaw 2.1.11 and SQLite 3.49.1 with it. 2.1.14 ships SQLite 3.54.
Only the native library moves: EF Core and Microsoft.Data.Sqlite stay at
10.0.0. The EfFloat lane drops the pin, since a floated patch brings its
own and a later one would fail the restore as a downgrade. Dependabot
ignores SQLitePCLRaw majors.

Closes #202

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 309429b)
@CaffeinatedCoder CaffeinatedCoder added this to the 5.6.1 milestone Oct 28, 2026
@CaffeinatedCoder CaffeinatedCoder added dependencies Pull requests that update a dependency file chore Build, CI, packaging, refactoring with no behaviour change package/core Affects EFCore.ComplexIndexes area/release Versioning, changelogs, release wiring labels Oct 28, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Versioning, changelogs, release wiring chore Build, CI, packaging, refactoring with no behaviour change dependencies Pull requests that update a dependency file package/core Affects EFCore.ComplexIndexes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant