CVE-2025-3277
An integer overflow can be triggered in SQLite’s function.
Published Apr 14, 2025 · updated Oct 15, 2026 · sqlite sqlite
An integer overflow can be triggered in SQLite’s function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can result in arbitrary code execution.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Apr 14, 2025 · NIST NVD
Detected
An integer overflow can be triggered in SQLite’s function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can result in arbitrary code execution.
Oct 15, 2026 · NIST NVD
Updated
An integer overflow can be triggered in SQLite’s function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can result in arbitrary code execution.
Affected
- cpe sqlite/sqliteversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2025-3277
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-3277
30-day exploitation probability 1.3%
first.org - NIST NVDVulnerability recordCVE-2025-3277
An integer overflow can be triggered in SQLite’s function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of
nvd.nist.gov