CVE-2025-6965 | Integer Truncation on SQLite

Exp

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.

Published: 2025-07-15 Last update: 2026-04-14 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-6965 is rated High Exploit Risk (72.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.69%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-6965

EDB-ID Source Kind Published Link
52499 exploit_db edb 2026-04-08 Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-6965

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-04 1.62% 1.69% +0.07%
2 2026-05-29 1.69% 1.62% -0.07%
3 2026-05-14 — 1.69% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-6965

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 4.0 HIGH
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:Green Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:H)
Exploitation depends on constrained or hard-to-reproduce conditions.
Attack requirements (AT:P)
Additional preconditions must be present for exploitation.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:L)
Limited confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:L)
Limited availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:L)
Limited confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:H)
High integrity impact on subsequent systems.
Subsequent system availability impact (SA:L)
Limited availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:N)
Negligible: impact meets the IEC 61508 negligible safety consequence category.
Automatable (supplemental) (AU:N)
No: attackers cannot reliably automate reconnaissance through exploitation for this issue.
Recovery (supplemental) (R:U)
User: manual user intervention is needed to recover services.
Value density (supplemental) (V:D)
Diffuse: a single exploit event controls relatively limited resources (e.g., one client).
Vulnerability response effort (supplemental) (RE:L)
Low/trivial response effort (documentation, simple configuration, low-touch guidance).
Provider urgency (supplemental) (U:GREEN)
Green: provider rates reduced urgency.
 — — [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2025-6965

OS Trackers for CVE-2025-6965

vendor priority summary link
alpine — CVE-2025-6965: 2 source package rows (qt6-qtwebengine, sqlite); 53 state rows across 7 repos (3.19-main, 3.20-main, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 7, open 46. https://security.alpinelinux.org/vuln/CVE-2025-6965
debian not yet assigned CVE-2025-6965 not yet assigned priority: Debian including 1 source packages (sqlite3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-6965
redhat high — https://access.redhat.com/security/cve/CVE-2025-6965
suse high CVE-2025-6965 severity important: SUSE including 334 source package names (0.23.1-11.34:libsqlite3-0-3.50.2-150000.3.33.1, 13.2-9.26:libpython3_11-1_0-3.11.11-1.1, …), 998 product×package rows across 353 product lines (Container bci/kiwi, Container bci/spack, … (353 product lines)): Fixed 767, Known Affected 226, Known Not Affected 5. https://www.suse.com/security/cve/CVE-2025-6965/
ubuntu medium CVE-2025-6965 medium priority: Ubuntu including 2 source packages (sqlite, sqlite3), 18 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 8, needs-triage 6, DNE 3, ignored 1. https://ubuntu.com/security/CVE-2025-6965

Affected software / configurations for CVE-2025-6965

Vendor Product Version Raw CPE
sqlite sqlite < 3.50.2 cpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*

References for CVE-2025-6965

cvelogic Threat Intelligence