CVE-2025-7709: SQLite FTS5 · Integer Overflow or Wraparound
Affects SQLite FTS5Source CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.50 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.50
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:H/VA:L/SC:N/SI:H/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade SQLite FTS5 to 3.50.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SQLite FTS5 | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-7709, European organizations should: 1) Upgrade SQLite to version 3.50 or later as soon as it becomes available, ensuring the integer overflow flaw in FTS5 is patched. 2) Conduct an inventory of applications and systems using SQLite with the FTS5 extension to identify vulnerable instances. 3) Implement strict input validation and sanitization to reduce the risk of malformed data triggering the overflow. 4) Employ runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to limit exploitation impact. 5) Monitor application logs and memory usage for anomalies indicative of exploitation attempts, focusing on full-text search operations. 6) Restrict network access to vulnerable services and enforce least privilege principles to reduce attack vectors. 7) Engage in security testing, including fuzzing and penetration testing, targeting SQLite FTS5 usage to detect potential exploitation. 8) Educate developers and system administrators about the vulnerability and encourage timely patch management. These steps go beyond generic advice by focusing on the specific extension and its usage context.
Description
An integer overflow exists in the FTS5 https://sqlite.org/fts5.html extension. It occurs when the size of an array of tombstone pointers is calculated and truncated into a 32-bit integer. A pointer to partially controlled data can then be written out of bounds.