CVE-2025-6965
Sqlite ≤ 3.50.2
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:D/RE:L/U:GreenSummary
CVE-2025-6965 is a high-severity Numeric Truncation Error (CWE-197) vulnerability in Sqlite Sqlite. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A vulnerability in SQLite versions prior to 3.50.2 allows the number of aggregate terms in a query to exceed the number of available columns, resulting in memory corruption. The flaw is tracked as CVE-2025-6965 and carries a CVSS 4.0 score of 7.2 with network attack vector, low privileges required, and high attack complexity.
An attacker who can supply or influence SQL statements processed by an affected SQLite instance may trigger the out-of-bounds condition. Successful exploitation can corrupt memory and produce high-integrity impacts on the affected process, though the high complexity and prerequisite access limit the practical attack surface to applications that accept untrusted queries or load attacker-controlled databases.
Public references, including the SQLite commit record and coordinated Full Disclosure postings, direct users to upgrade to version 3.50.2 or later to correct the aggregate-term handling logic. The associated EPSS score remains low at approximately 0.017 with no material increase after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21441
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover truncation errors through static analysis, dynamic testing, or code review.
Documented development standards and tools can mandate use of safe arithmetic libraries or explicit checks against truncation.
Engineering principles can require safe type conversions and avoidance of narrowing casts that cause truncation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent truncation errors via reviews, static analysis, and safe type handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect truncation bugs through static analysis and fuzzing.
Secure development lifecycle mandates practices that can catch numeric truncation during design and code review.
Application security requirements can specify safe numeric handling and data-type constraints.
Secure architecture principles include choosing appropriate data types and avoiding unsafe casts.
Secure coding standards directly prohibit unsafe narrowing conversions and truncation.