High · published July 15, 2025
CVSS calls it high at 7.7. It sits in the 99.5th percentile for exploit probability.
⚡ It turns out SQLite had a bit of a party problem! In versions before 3.50.2, too many aggregate terms can lead to a wild memory corruption issue. 🎉 Think of it as trying to fit too many guests into a tiny elevator — when the load exceeds the capacity, things can get messy! This could cause the application to crash or behave unpredictably, potentially leading to data loss or corruption. In the worst-case scenario, your application’s reliability could be compromised, leaving you in a bind.
Think of it as trying to fit too many guests into a tiny elevator — when the load exceeds the capacity, things can get messy! This vulnerability occurs when the number of aggregate terms in an SQLite query exceeds the number of available columns, resulting in memory corruption during execution.
This could cause the application to crash or behave unpredictably, potentially leading to data loss or corruption. In the worst-case scenario, your application’s reliability could be compromised, leaving you in a bind. Upgrade your SQLite to version 3.50.2 or above immediately to close this vulnerability. Regularly audit your database queries for best practices to ensure stability. You've got this! Take those steps, and you'll have your database running smoothly in no time. 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| sqlite/sqlite | < 3.50.2 | 3.50.2 |
| apple/ipados | < 26.0.0 | 26.0.0 |
| apple/iphone_os | < 26.0.0 | 26.0.0 |
| apple/macos | < 26.0.0 | 26.0.0 |
| apple/tvos | < 26.0.0 | 26.0.0 |
| apple/visionos | < 26.0.0 | 26.0.0 |
| apple/watchos | < 26.0.0 | 26.0.0 |
| siemens/ruggedcom_crossbow | < 5.8 | 5.8 |
| siemens/sidis_prime | < 4.0.800 | 4.0.800 |