# CVE-2026-11824: SQLite before 3.53.2 Heap Buffer Overflow via FTS5 fts5ChunkIterate

> Attackers can execute arbitrary code or cause crashes in applications using SQLite with FTS5 enabled by providing a crafted database file.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2026-11824, AZL-89703, BELL-CVE-2026-11824, BIT-sqlite-2026-11824, DEBIAN-CVE-2026-11824, ECHO-3be4-5309-fe51, GHSA-8g48-4wfm-7247, MINI-cp3r-rp4g-f926, ROOT-OS-ALPINE-318-CVE-2026-11824, ROOT-OS-ALPINE-319-CVE-2026-11824, ROOT-OS-ALPINE-320-CVE-2026-11824, ROOT-OS-ALPINE-321-CVE-2026-11824, ROOT-OS-ALPINE-322-CVE-2026-11824, ROOT-OS-DEBIAN-11-CVE-2026-11824, ROOT-OS-DEBIAN-12-CVE-2026-11824, UBUNTU-CVE-2026-11824

## What is CVE-2026-11824?

CVE-2026-11824 is a high-severity memory corruption vulnerability in Sqlite Sqlite, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SQLite before 3.53.2 contains a heap-based buffer overflow vulnerability in the FTS5 full-text search extension that allows attackers to cause a crash or execute arbitrary code by supplying a crafted database with malicious continuation page metadata specifying a szLeaf value smaller than 4. Attackers can trigger an integer underflow in fts5ChunkIterate() causing an inflated remaining byte count during FTS5 MATCH query processing, leading to a heap buffer overflow of attacker-controlled data in applications compiled with SQLITE_ENABLE_FTS5.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-11824?

1 open source package ship an affected version, including sqlite. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqlite` | Bitnami | All versions | 3.53.2 |

Products: Sqlite Sqlite.

## How do I fix CVE-2026-11824?

Upgrade sqlite to 3.53.2 or later.

## Is CVE-2026-11824 being exploited?

There is no known exploitation of CVE-2026-11824 in the wild and no public exploit code.

## Other vulnerabilities in Sqlite Sqlite

- [CVE-2015-5895](https://insights.sbomify.com/CVE-2015-5895/): Other in n/a (critical 10.0)
- [CVE-2017-10989](https://insights.sbomify.com/CVE-2017-10989/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-11822](https://insights.sbomify.com/CVE-2026-11822/): SQLite before 3.53.2 Memory Corruption in FTS5 Extension (high 8.5)
- [CVE-2025-70873](https://insights.sbomify.com/CVE-2025-70873/): Information disclosure in n/a (high 7.5)
- [CVE-2021-31239](https://insights.sbomify.com/CVE-2021-31239/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11824 and fix it if it is affected.

What it is: CVE-2026-11824 is a high-severity memory corruption vulnerability in Sqlite Sqlite, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-11824 in the wild and no public exploit code.

Affected packages and fixed versions:
- sqlite (Bitnami): affected all versions; fixed in 3.53.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11824/ (Markdown: https://insights.sbomify.com/CVE-2026-11824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11824
- OSV: https://osv.dev/vulnerability/CVE-2026-11824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11824/
Summaries are generated and may contain mistakes; the official description above is the record.