CVE-2026-119372

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-30. A secondary CVSS source baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-113783 (ENISA EUVD) · GHSA-p82x-8j2g-f2c7 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process.

CVSS v3
5.5
EG Score
5.5MEDIUMhigh confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

November 4, 2026

Advisory Details (7)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit.
Web page

SQLite before 3.54.0 Use-After-Free in FTS3 fts3BestSnippet() via snippet() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sqlite-before-3.54.0-use-after-free-in-fts3-fts3bestsnippet-via-snippet
Web page

SQLite: Check-in [e4635c4153]

https://sqlite.org/src/info/e4635c4153
Web page

SQLite Release 3.54.0 On 2026-10-09

https://sqlite.org/releaselog/3_54_0.html
Web page

SQLite Bug Forum: UAF in FTS3/FTS4 snippet()

https://sqlite.org/bugs/info/2026-08-17T09:18:24Z
GitHub commit

commit a87bd2471a9c (sqlite/sqlite)

Fix landed in sqlite/sqlite commit a87bd2471a9c — awaiting tagged release

https://github.com/sqlite/sqlite/commit/a87bd2471a9c0606e78d3c3678bcd9cecaa0e731
Web page

sqlite/ext/fts3/fts3_snippet.c at version-3.53.4 · sqlite/sqlite · GitHub

https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/fts3/fts3_snippet.c#L561
Web page

GitHub - sqlite/sqlite: Official Git mirror of the SQLite source tree · GitHub

https://github.com/sqlite/sqlite

Vendor Advisories for CVE-2026-119372(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite33.40.1-2 ... 3.54.1-1 (30 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite33.46.1-7 ... 3.54.1-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sqlite33.46.1-7 ... 3.54.1-1 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-11-11 06:58 UTCEchelonGraph re-scored
  4. 2026-11-11 06:58 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub severity MODERATE · GitHub CVSS 5.5
  5. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-11-04 02:25 UTCEchelonGraph re-scored
  13. 2026-11-04 02:25 UTCVendor advisory
  14. 2026-11-04 02:25 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub severity MODERATE · GitHub CVSS 5.5
  15. 2026-11-04 02:11 UTCEchelonGraph re-scored
  16. 2026-11-04 02:11 UTCVendor advisory
  17. 2026-11-04 02:11 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub severity MODERATE · GitHub CVSS 5.5
  18. 2026-11-04 01:49 UTCEchelonGraph re-scored
  19. 2026-11-04 01:49 UTCVendor advisory
  20. 2026-11-04 01:49 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub severity MODERATE · GitHub CVSS 5.5
  21. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-11-03 16:28 UTCEchelonGraph re-scored
  23. 2026-11-03 16:28 UTCVendor advisory
  24. 2026-11-03 16:28 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub severity MODERATE · GitHub CVSS 5.5
  25. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 8 more
  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-30 18:47 UTCEchelonGraph re-scored
  4. 2026-10-30 18:47 UTCGHSA enrichmentGHSA-p82x-8j2g-f2c7 · GitHub CVSS 5.5
  5. 2026-10-30 12:26 UTCEchelonGraph re-scored
  6. 2026-10-30 12:02 UTCENISA EUVD ID recordedEUVD-2026-113783 · Source: ENISA EUVD
  7. 2026-10-30 11:36 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
  8. 2026-10-30 11:35 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-119372?
CVE-2026-119372 is a medium-severity vulnerability; its CVE record was published on October 30, 2026. SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap…
When was CVE-2026-119372 made public?
CVE-2026-119372 was made public on August 17, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 30, 2026. EchelonGraph's copy of the record carries a last-modified date of November 4, 2026; the record at its source may have been updated since.
Is CVE-2026-119372 actively exploited?
CVE-2026-119372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119372?
CVE-2026-119372 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119372?
A fix for CVE-2026-119372 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119372 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-119372

Explore →

Is Your Infrastructure Affected by CVE-2026-119372?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs