dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-7709

MEDIUM · 6.9 CVSS v4.0 Published 2025-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An integer overflow vulnerability exists in SQLite's FTS5 extension where the calculation of an array of tombstone pointers is truncated to a 32-bit integer. This causes the array size calculation to wrap around, allowing a pointer to partially controlled data to be written out of bounds, leading to potential memory corruption.

MitigationUpdate SQLite to a version that includes the fix for this integer overflow. If unable to update immediately, restrict untrusted input from being processed by the FTS5 extension.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
Authentication
X
User interaction
A
Scope
X

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/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:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed SQLite version
    Run 'sqlite3 --version' or check the shared library version (e.g., libsqlite3.so) using 'ldd' or 'dpkg -l libsqlite3-0' on Linux, or check the application bundling. Compare the version number to the fixed release that contains the CVE-2025-7709 patch.
    Affected if The installed SQLite version is older than the version that includes the fix for CVE-2025-7709 (the fix version is not specified in provided data; treat any pre-2025 version as potentially affected).
  2. Verify FTS5 extension is enabled
    Run 'sqlite3' and execute 'SELECT load_extension();' or check if FTS5 is available with 'SELECT fts5()' or by querying 'PRAGMA compile_options' for 'ENABLE_FTS5'. Alternatively, check if the SQLite library was compiled with FTS5 support by inspecting the library binary or documentation.
    Affected if FTS5 is compiled into or loaded by the SQLite installation and the SQLite version is vulnerable.
  3. Identify FTS5 virtual tables in use
    Query all databases for FTS5 tables using 'SELECT name FROM sqlite_master WHERE type="table" AND sql LIKE "%fts5%"' in each database file. If using an application, review its database schema or configuration for CREATE VIRTUAL TABLE ... USING fts5 statements.
    Affected if Any FTS5 virtual tables exist in the environment and the SQLite version is vulnerable.
  4. Check for FTS5 query processing of untrusted input
    Review application code or SQL query logs to determine if FTS5 tables process data or search queries originating from untrusted external sources (user input, network data, uploaded files). Inspect query patterns for FTS5 MATCH or INSERT/UPDATE operations on FTS5 tables.
    Affected if FTS5 tables accept and process untrusted input and the SQLite version is vulnerable.

An environment is affected if it runs a vulnerable SQLite version with FTS5 extension enabled and processes data through FTS5 virtual tables, particularly from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SQLite to a version that includes the fix for this integer overflow. If unable to update immediately, restrict untrusted input from being processed by the FTS5 extension.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data