How severe is CVE-2025-6965?

No CVSS score has been assigned to CVE-2025-6965 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-6965?

CVE-2025-6965 affects the following packages: SQLitePCLRaw.lib.e_sqlite3 (NuGet), SQLitePCLRaw.lib.e_sqlite3.android (NuGet), SQLitePCLRaw.lib.e_sqlite3.ios (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2025-6965?

No patched version of SQLitePCLRaw.lib.e_sqlite3 has shipped for CVE-2025-6965 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2025-6965 in my NuGet dependencies?

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.

How do I mitigate CVE-2025-6965 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2025-6965?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-6965 can be triaged on real exposure rather than presence alone.

Is CVE-2025-6965 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-6965, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-6965?

CVE-2025-6965 has an EPSS (Exploit Prediction Scoring System) score of 72.5%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2025-6965?

CVE-2025-6965 is classified as CWE-197 (CWE-197). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-6965 published, and has it been updated?

CVE-2025-6965 was published on July 15, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

CVE-2025-6965 — SQLitePCLRaw.lib.e_sqlite3

CVE-2025-6965 is a 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.

Integer Truncation on SQLite

Also known asBIT-sqlite-2025-6965GHSA-2m69-gcr7-jv3q

Published

Jul 15, 2025

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

None yet

Exploits

1 known

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2025-6965.

EPSS Exploitation Probability

via FIRST.org ↗

72.5%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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.

Real-World Exposure

3 pkgs affected

.NETSQLitePCLRaw.lib.e_sqlite3.NETSQLitePCLRaw.lib.e_sqlite3.android.NETSQLitePCLRaw.lib.e_sqlite3.ios

Real-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

3 total

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52499localwindows

SQLite 3.50.1 - Heap Overflow

by Mohammed Idrees Banyamer · Apr 8, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2025-6965 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 CVE-2025-6965 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-6965. 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.

Red HatImportant

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

O3 Security · Impact-Aware SCA

Is CVE-2025-6965 in your dependencies?

O3 Security finds CVE-2025-6965 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works