CVE-2025-52099
Published: October 25, 2025Last modified: December 23, 2025
Description
Integer Overflow vulnerability in SQLite SQLite3 v.3.50.0 allows a remote attacker to cause a denial of service via the setupLookaside function
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.5 |
| Attack Vector | NETWORK |
| Attack complexity | LOW |
| Privileges required | NONE |
| User interaction | NONE |
| Scope | UNCHANGED |
| Confidentiality | NONE |
| Integrity impact | NONE |
| Availability impact | HIGH |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Notes
The only information officially available so far is that "Integer Overflow vulnerability in SQLite SQLite3 v.3.50.0 allows a remote attacker to cause a denial of service via the setupLookaside function". NB: This CVE seems to be bogus security spam. The problem is already reported as CVE-2025-29088 with proper affected version numbers. As SQLite author explains in a forum thread the problem was introduced in 3.49 https://sqlite.org/forum/forumpost/48f365daec7e50af01350d72c19c317f02e5fc0d3b1e778256d1fbd8081eec5d > The fix first appeared in the 3.49.1 release. > > This is not a serious issue. It involves using out-of-bounds > parameters to a C-level API which is not accessible to hackers via > SQL inputs or custom databases. It requires the ability to run C > code. And if the attacker can run C code, then you already have > other problems.
Status
| Product | Release | Package | Status |
|---|---|---|---|
| Alpaquita Linux | 23 LTS | sqlite | Not affected (3.40.0-r0) |
| 25 LTS | sqlite | Not affected (3.49.2-r0) | |
| Stream | sqlite | Fixed (3.49.1-r0) | |
| Hardened Containers | 23 LTS | sqlite | Not affected (3.40.0-r0) |
| 25 LTS | sqlite | Not affected (3.49.2-r0) | |
| Stream | sqlite | Fixed (3.49.1-r0) |