And we now have 3.41.2: https://sqlite.org/releaselog/3_41_2.html Multiple fixes for reads past the end of memory buffers (NB: reads not writes) in the following circumstances: When processing a corrupt database file using the non-standard SQLITE_ENABLE_STAT4 compile-time option. In the CLI when the sqlite3_error_offset() routine returns an out-of-range value (see also the fix to sqlite3_error_offset() below). In the recovery extension. In FTS3 when processing a corrupt database file. Fix the sqlite3_error_offset() so that it does not return out-of-range values when reporting errors associated with generated columns. Multiple fixes in the query optimizer for problems that cause incorrect results for bizarre, fuzzer-generated queries. Increase the size of the reference counter in the page cache object to 64 bits to ensure that the counter never overflows. Fix a performance regression caused by a bug fix in patch release 3.41.1. Fix a few incorrect assert() statements.
Bug 1821683 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
And we now have 3.41.2: https://sqlite.org/releaselog/3_41_2.html - Multiple fixes for reads past the end of memory buffers (NB: reads not writes) in the following circumstances: a. When processing a corrupt database file using the non-standard SQLITE_ENABLE_STAT4 compile-time option. b. In the CLI when the sqlite3_error_offset() routine returns an out-of-range value (see also the fix to sqlite3_error_offset() below). c. In the recovery extension. d. In FTS3 when processing a corrupt database file. - Fix the sqlite3_error_offset() so that it does not return out-of-range values when reporting errors associated with generated columns. - Multiple fixes in the query optimizer for problems that cause incorrect results for bizarre, fuzzer-generated queries. - Increase the size of the reference counter in the page cache object to 64 bits to ensure that the counter never overflows. - Fix a performance regression caused by a bug fix in patch release 3.41.1. - Fix a few incorrect assert() statements.
<removed> Saw that you already notice.