CVE-2026-11822

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds read in fts5LeafSeek() via an attacker-controlled loop bound and a heap buffer overflow write in fts5ChunkIterate() through a crafted continuation page causing an integer underflow, exploitable when an FTS5 MATCH query is executed against the malicious database.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 9, 2026
No patch confirmed yet.
generic

SQLite before 3.53.2 Memory Corruption in FTS5 Extension | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sqlite-before-memory-corruption-in-fts5-extension
generic

SQLite: Check-in [4a5ad516ea]

https://sqlite.org/src/info/4a5ad516ea93
generic

SQLite: Check-in [061febcf41]

https://sqlite.org/src/info/061febcf41ca
generic

SQLite Release 3.53.2 On 2026-06-03

https://sqlite.org/releaselog/3_53_2.html

Vendor Advisories for CVE-2026-11822(13)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusqlite3-tools (3.46.1-9ubuntu0.1) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
sqlite33.34.1-3 ... 3.53.4-2 (52 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
sqlite33.40.1-2 ... 3.53.4-2 (29 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sqlite33.46.1-7 ... 3.53.4-2 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sqlite33.46.1-7, 3.46.1-8, 3.46.1-93.53.2-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 122× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 325 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:21 UTCEPSS rescore
  3. 2026-08-28 21:40 UTCEPSS rescore
  4. 2026-08-27 14:24 UTCEPSS rescore
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-25 00:47 UTCEG score recompute
  7. 2026-08-25 00:47 UTCVendor advisory
  8. 2026-08-25 00:47 UTCGHSA enrichment
  9. 2026-08-23 23:28 UTCVendor advisory
  10. 2026-08-23 23:28 UTCGHSA enrichment
  11. 2026-08-23 11:02 UTCEG score recompute
  12. 2026-08-23 11:02 UTCVendor advisory
  13. 2026-08-23 11:02 UTCGHSA enrichment
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-21 22:45 UTCVendor advisory
  17. 2026-08-21 22:45 UTCGHSA enrichment
  18. 2026-08-21 10:00 UTCEG score recompute
  19. 2026-08-21 10:00 UTCVendor advisory
  20. 2026-08-21 10:00 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 21:21 UTCVendor advisory
  23. 2026-08-20 21:21 UTCGHSA enrichment
  24. 2026-08-20 08:56 UTCEG score recompute
  25. 2026-08-20 08:56 UTCVendor advisory
Show 75 more
  1. 2026-08-20 08:56 UTCGHSA enrichment
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-19 15:41 UTCEG score recompute
  4. 2026-08-19 15:41 UTCVendor advisory
  5. 2026-08-19 15:41 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 12:42 UTCVendor advisory
  8. 2026-08-17 12:42 UTCGHSA enrichment
  9. 2026-08-17 00:17 UTCEG score recompute
  10. 2026-08-17 00:17 UTCVendor advisory
  11. 2026-08-17 00:17 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 04:53 UTCEG score recompute
  14. 2026-08-16 04:53 UTCVendor advisory
  15. 2026-08-16 04:53 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 16:29 UTCVendor advisory
  18. 2026-08-15 16:29 UTCGHSA enrichment
  19. 2026-08-15 04:05 UTCEG score recompute
  20. 2026-08-15 04:05 UTCVendor advisory
  21. 2026-08-15 04:05 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 15:41 UTCVendor advisory
  24. 2026-08-14 15:41 UTCGHSA enrichment
  25. 2026-08-14 03:16 UTCEG score recompute
  26. 2026-08-14 03:16 UTCVendor advisory
  27. 2026-08-14 03:16 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-13 14:52 UTCVendor advisory
  30. 2026-08-13 14:52 UTCGHSA enrichment
  31. 2026-08-13 02:00 UTCEG score recompute
  32. 2026-08-13 02:00 UTCVendor advisory
  33. 2026-08-13 02:00 UTCGHSA enrichment
  34. 2026-08-12 13:50 UTCEPSS rescore
  35. 2026-08-12 13:36 UTCVendor advisory
  36. 2026-08-12 13:36 UTCGHSA enrichment
  37. 2026-08-12 01:00 UTCEG score recompute
  38. 2026-08-12 01:00 UTCVendor advisory
  39. 2026-08-12 01:00 UTCGHSA enrichment
  40. 2026-08-11 13:42 UTCEPSS rescore
  41. 2026-08-11 12:36 UTCVendor advisory
  42. 2026-08-11 12:36 UTCGHSA enrichment
  43. 2026-08-11 00:09 UTCEG score recompute
  44. 2026-08-11 00:09 UTCVendor advisory
  45. 2026-08-11 00:09 UTCGHSA enrichment
  46. 2026-08-10 23:59 UTCEPSS rescore
  47. 2026-08-10 11:45 UTCVendor advisory
  48. 2026-08-10 11:45 UTCGHSA enrichment
  49. 2026-08-09 23:21 UTCEG score recompute
  50. 2026-08-09 23:21 UTCVendor advisory
  51. 2026-08-09 23:21 UTCGHSA enrichment
  52. 2026-08-09 13:46 UTCEPSS rescore
  53. 2026-08-09 10:57 UTCVendor advisory
  54. 2026-08-09 10:57 UTCGHSA enrichment
  55. 2026-08-08 22:32 UTCEG score recompute
  56. 2026-08-08 22:32 UTCVendor advisory
  57. 2026-08-08 22:32 UTCGHSA enrichment
  58. 2026-08-08 16:37 UTCEPSS rescore
  59. 2026-08-08 10:07 UTCVendor advisory
  60. 2026-08-08 10:07 UTCGHSA enrichment
  61. 2026-08-07 21:43 UTCEG score recompute
  62. 2026-08-07 21:43 UTCVendor advisory
  63. 2026-08-07 21:43 UTCGHSA enrichment
  64. 2026-08-07 09:19 UTCVendor advisory
  65. 2026-08-07 09:19 UTCGHSA enrichment
  66. 2026-08-06 20:55 UTCEG score recompute
  67. 2026-08-06 20:55 UTCVendor advisory
  68. 2026-08-06 20:55 UTCGHSA enrichment
  69. 2026-08-06 13:46 UTCEPSS rescore
  70. 2026-08-06 08:31 UTCVendor advisory
  71. 2026-08-06 08:31 UTCGHSA enrichment
  72. 2026-08-05 20:06 UTCEG score recompute
  73. 2026-08-05 20:06 UTCVendor advisory
  74. 2026-08-05 20:06 UTCGHSA enrichment
  75. 2026-08-05 19:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-11822?
CVE-2026-11822 is a high vulnerability published on June 9, 2026. SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds…
When was CVE-2026-11822 disclosed?
CVE-2026-11822 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11822 actively exploited?
CVE-2026-11822 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.9% of all scored CVEs.
What is the CVSS score of CVE-2026-11822?
CVE-2026-11822 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-11822?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11822, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11822?

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

Start Free Scan →Browse All CVEs