5648 matches found
CVE-2026-51297
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51298
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51303
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
EUVD-2026-49351
SQLite 3.41 has a use-after-free vulnerability in jsonRemoveFunc of SQLite JSON module. The parsed JSON object is freed at line 3555, while line 3575 still calls jsonLookupStep with the released pointer. Remote attackers can exploit this flaw to crash the service and leak heap memory information...
EUVD-2026-49353
sqlite 3.41 is vulnerable to use after free in the JSON extraction function. After releasing JsonParse object memory via jsonParseFree, the program still accesses internal member of the freed pointer, which can cause service crash and denial of service...
CVE-2026-51302
SQLite 3.41 contains a use-after-free in the expression evaluation logic: sqlite3ReleaseTempReg frees temporary registers, but exprComputeOperands may access freed memory. This could allow a remote attacker to cause DoS, leak data, or potentially execute arbitrary code. The connected docs do not ...
CVE-2026-51304
sqlite 3.41 has a use-after-free UAF vulnerability in the ORDER BY clause parsing routine. The affected code first releases the memory of an ExprList object via sqlite3ExprListDelete, then attempts to access the nExpr member of the already freed object. This dangling pointer access causes invalid...
EUVD-2026-49354
A use-after-free vulnerability exists in the expression parsing and memory management logic of SQLite 3.41. After invoking sqlite3ExprDelete to release an expression object, the program still retains the dangling pointer and subsequently accesses member fields of the already freed memory. By...
CVE-2026-51300
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51297
This CVE entry is rejected/not used and does not represent an active vulnerability.
CVE-2026-51300
SQLite 3.41 contains a use-after-free vulnerability in the expression parsing/memory management logic. Specifically, after sqlite3ExprDelete releases an expression object, the program may still access freed memory in expr.c, allowing a remote attacker to craft malicious SQL queries that trigger i...
CVE-2026-51302
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51296
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51304
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none...
CVE-2026-51298
Summary of findings (CVE-2026-51298) : Several connected advisories confirm a use-after-free vulnerability in SQLite 3.41 related to the JSON extraction function. The flaw occurs when, after releasing the JsonParse object with jsonParseFree(), the code still accesses internal members of the freed...