Skip to content

SQLitePCLRaw.core/2.1.12 is available #9

Closed

Description

@JasonLandbridge

Hi there!

Thank you for this awesome package and just what I needed!

While setting it up I came across this commit:

9fe1515

It states that 2.1.11 is the latest release, this is correct if you look at the GitHub releases but there is (since 5 days ago) a NuGet release which I believe address the vulnerability: https://www.nuget.org/packages/SQLitePCLRaw.core/2.1.12

I tested it locally and by installing this version it resolves the vulnerability warning.

Activity

  1. CornerstoneCode commented on Oct 5, 2026

    @CornerstoneCode
    Owner

    ✓ Issue Resolved: v10.1.1 Released

    Hi @JasonLandbridge!

    Thank you for the detailed report and for reaching out about the SQLitePCLRaw.core update. You were absolutely right — 2.1.12 is now available on NuGet and addresses the vulnerability (GHSA-2m69-gcr7-jv3q).

    What We Did

    v10.1.1 Security Patch is now released with:

    ✅ Security Fix

    • Upgraded SQLitePCLRaw.core: 2.1.11 → 2.1.12
    • Vulnerability fixed: GHSA-2m69-gcr7-jv3q
    • All transitive SQLitePCLRaw packages verified at 2.1.12
    • Removed the vulnerability suppression comment from the project file

    ✅ Quality & Compatibility

    • Zero API changes (drop-in upgrade)
    • Zero breaking changes
    • Fully backward compatible with v10.1.0
    • Build verified with 0 errors
    • No migration required

    ✅ Enhanced Discoverability

    • Optimized package description with security disclosure
    • Expanded tags for better NuGet search visibility
    • Clear release notes and CHANGELOG entries

    Get the Update

    Via NuGet CLI:
    \\�ash
    dotnet package update EntityFrameworkCore.Sqlite.Concurrency
    \\

    Via Package Manager:
    \
    Update-Package EntityFrameworkCore.Sqlite.Concurrency
    \\

    Where to Find It


    Thank you again for your vigilance on this! Your early detection and report helped us ship a proper security patch with quality documentation. We really appreciate contributors like you who care about keeping dependencies current and secure. 🙏

    If you have any other issues or suggestions, feel free to open an issue or reach out!


    This issue will be automatically closed when PR #13 merges to main.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions