# CVE-2025-7709: Out Of Bounds write in FTS5 Extension in SQLite

> An integer overflow in SQLite's FTS5 extension allows out-of-bounds writes, potentially enabling arbitrary code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2025
- **Updated:** 18 Nov 2025
- **Also known as:** BELL-CVE-2025-7709, DEBIAN-CVE-2025-7709, ECHO-37b8-7d67-9685, GHSA-v2c8-vqqp-hv3g, ROOT-OS-DEBIAN-12-CVE-2025-7709, SUSE-SU-2026:0395-1, SUSE-SU-2026:0432-1, UBUNTU-CVE-2025-7709, USN-7751-1, openSUSE-SU-2026:10171-1

## What is CVE-2025-7709?

CVE-2025-7709 is a medium-severity vulnerability in SQLite FTS5, published on 8 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-7709?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqlite3` | SUSE:Linux Enterprise Micro 5.2 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | SUSE:Linux Enterprise Micro 5.3 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | SUSE:Linux Enterprise Micro 5.4 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | SUSE:Linux Enterprise Micro 5.5 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.51.2-9.44.1 |
| `sqlite3` | openSUSE:Leap 15.6 | All versions | 3.51.2-150000.3.36.1 |
| `sqlite3` | openSUSE:Tumbleweed | All versions | 3.51.2-1.1 |

## How do I fix CVE-2025-7709?

Apply the vendor's patch.

## Is CVE-2025-7709 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7709 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7709 and fix it if it is affected.

What it is: CVE-2025-7709 is a medium-severity vulnerability in SQLite FTS5, published on 8 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7709 exists.

Affected product: SQLite FTS5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7709/ (Markdown: https://insights.sbomify.com/CVE-2025-7709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7709
- OSV: https://osv.dev/vulnerability/CVE-2025-7709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7709/
Summaries are generated and may contain mistakes; the official description above is the record.