CVE-2026-119374 json
SQLite before 3.54.0 Heap Buffer Overflow via FTS5 fts5DoSecureDelete()
published 2026-10-30 10 d ago modified 2026-11-03 6 d ago also EUVD-2026-113785
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.
Patch / fix
- SQLite SQLite 3.54.0
- sqlite3 openSUSE Tumbleweed 3.54.1-2.1
opensuse advisories openSUSE-SU-2026:12493-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-119374 updated cvss 7.8
sqlite: sqlite: Arbitrary code execution via corrupted FTS5 index
-
Red Hat Enterprise Linux 6 lemon, sqlite, sqlite-tcl, sqlite 3.46.1-6.el10_2 Red Hat Enterprise Linux 7 lemon, sqlite, sqlite-tcl, sqlite 3.46.1-6.el10_2 Red Hat Enterprise Linux 8 npm, lemon, nodejs, sqlite, nodejs-libs, sqlite-libs, +8 more Red Hat Enterprise Linux 9 npm, rust, cargo, clippy, nodejs, sqlite, +15 more Red Hat Enterprise Linux 10 sqlite 3.46.1-6.el10_2 Red Hat Enterprise Linux AI (RHEL AI) 3 rustaffected: no fix available
+3 more productsfewer
Red Hat Hardened Images sqlite 3.46.1-6.el10_2 Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9 -
Red Hat Enterprise Linux AppStream (v. 9) nodejs 24.22.1-5.module+el9.8.0+25292+33251f3b, nodejs-libs 24.22.1-5.module+el9.8.0+25292+33251f3b, nodejs-nodemon 3.1.14-6.module+el9.8.0+25292+33251f3b, npm 11.19.1-1.24.22.1.5.module+el9.8.0+25292+33251f3b, nodejs-full-i18n 24.22.1-5.module+el9.8.0+25292+33251f3b, nodejs-packaging 2021.06-6.module+el9.8.0+24708+e71d2e1d, +1 morefixed: vendor fix RHSA-2026:96226
-
Red Hat Enterprise Linux 8 rls, rust, cargo, clippy, rustfmt, rust-gdb, +8 morenot affected: vulnerable code not in execute path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 10 d ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- abraxaslabs.tech https://abraxaslabs.tech/research/sqlite-fts5-securedel referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.5 | 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 |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 8.5 | 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/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 |
Affected products
- SQLite SQLite
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
sqlite.org
/src/info/9cd4f9e920
patch, vendor-advisory
-
github.com
/sqlite/sqlite/commit/d9de6eedbe918c074c7556400fa21df5960704d9
patch
-
github.com
/sqlite/sqlite/blob/version-3.53.4/ext/fts5/fts5_index.c#L5525
technical-description, patch
-
abraxaslabs.tech
/research/sqlite-fts5-securedel
third-party-advisory, exploit
-
sqlite.org
/releaselog/3_54_0.html
release-notes
-
github.com
/sqlite/sqlite
product
-
vulncheck.com
/advisories/sqlite-before-3.54.0-heap-buffer-overflow-via-fts5-fts5dosecuredelete
third-party-advisory
Sources
- CVE List CVE-2026-119374
- NVD CVE-2026-119374
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.