Skip to main content
VulnerabilityPublished

CVE-2026-119374: SQLite before 3.54.0 Heap Buffer Overflow via FTS5 fts5DoSecureDelete()

Affects sqliteSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119374· High 8.5

Not known to be exploited · CVSS 8.5 High : upgrade to 3.54.0 soon.

Data as of 17 Nov 2026, 16:18 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.5
CNA (VulnCheck)CVSS 3.17.8
CNACVSS 4.08.5
Patch
Available – fixed in 3.54.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade sqlite to 3.54.0.

Affected software

ProductAffectedFixed in
Bitnamisqlitepkg:bitnami/sqliteOther threatsAffected
  • <3.54.0
Fixed in
  • 3.54.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SQLite to version 3.54.0 or later, where this vulnerability is fixed. The patch is publicly available and should be applied to prevent exploitation. No other mitigations are indicated.

Description

SQLite versions before 3.54.0 that are built with the FTS5 extension contain a heap buffer overflow vulnerability in the fts5DoSecureDelete() function. This flaw allows attackers to write beyond the leaf page buffer by supplying a database file with a corrupted FTS5 index. When secure-delete is enabled and a deletion is performed, heap memory corruption occurs, potentially crashing the application.

References

Community reviews

Loading reviews…