PT-2026-65540 · Sqlite3 · Sqlite3
CVE-2026-54619
·
Published
2026-07-28
·
Updated
2026-07-28
CVSS v4.0
2.0
Low
| Vector | AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N |
Name of the Vulnerable Software and Affected Versions
sqlite3 versions prior to 2.9.5
Description
Redefining a SQLite function with a different arity (the number of arguments a function takes) or different text encodings using
Database#create function() or Database#define function() causes the previously registered function handler to be freed while SQLite may still reference it. This leads to a use-after-free condition, which can result in an invalid memory read and a segmentation fault.Recommendations
Update to version 2.9.5 or later.
As a temporary workaround, avoid defining multiple custom functions with the same name using varying numbers of arguments or encoding.
Exploit
Fix
Use After Free
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Sqlite3