GHSA-2m69-gcr7-jv3q is a critical-severity (CVSS 9.8) CWE-197 vulnerability in SQLitePCLRaw.lib.e_sqlite3. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
SQLitePCLRaw.lib.e_sqlite3 has a vulnerable dependency on SQLite
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2m69-gcr7-jv3q.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2m69-gcr7-jv3q plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
SQLitePCLRaw.lib.e_sqlite3.NETSQLitePCLRaw.lib.e_sqlite3.android.NETSQLitePCLRaw.lib.e_sqlite3.iosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | SQLitePCLRaw.lib.e_sqlite3 | all versions | No fix |
| .NETNuGet | SQLitePCLRaw.lib.e_sqlite3.android | all versions | No fix |
| .NETNuGet | SQLitePCLRaw.lib.e_sqlite3.ios | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
SQLite 3.50.1 - Heap Overflow
by Mohammed Idrees Banyamer · Apr 8, 2026
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for SQLitePCLRaw.lib.e_sqlite3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of SQLitePCLRaw.lib.e_sqlite3 has shipped for GHSA-2m69-gcr7-jv3q yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2m69-gcr7-jv3q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2m69-gcr7-jv3q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability in SQLite is categorized as Important rather than Critical because, although it involves memory corruption, the conditions required to trigger it are relatively constrained. The flaw arises when a query causes the number of aggregate terms to exceed internal limits, leading to potential buffer…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | sqlite-0:3.46.1-5.el10_0 | RHSA-2025:11933 |
| Red Hat Enterprise Linux 7 Extended Lifecycle Support | sqlite-0:3.7.17-9.el7_9.1 | RHSA-2025:12349 |
| Red Hat Enterprise Linux 8 | nodejs:22-8100020250717142920.6d880403 | RHSA-2025:11803 |
| Red Hat Enterprise Linux 8 | sqlite-0:3.26.0-20.el8_10 | RHSA-2025:12010 |
| Red Hat Enterprise Linux 8 | mingw-sqlite-0:3.26.0.0-2.el8_10 | RHSA-2025:14101 |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | sqlite-0:3.26.0-6.el8_2.1 | RHSA-2025:12901 |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | spice-client-win-0:8.10-3.el8_2.1 | RHSA-2026:0078 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | sqlite-0:3.26.0-13.el8_4.1 | RHSA-2025:12905 |
Frequently Asked Questions
Is GHSA-2m69-gcr7-jv3q in your dependencies?
O3 Security finds GHSA-2m69-gcr7-jv3q across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.