There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found in SQLite up to 3.50.1. It has been rated as problematic.Using CWE to declare the problem leads to CWE-197. Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found in SQLite up to 3.50.1. It has been rated as problematic.Using CWE to declare the problem leads to CWE-197. Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found in SQLite up to 3.50.1. It has been rated as problematic.Using CWE to declare the problem leads to CWE-197. Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found in SQLite up to 3.50.1. It has been rated as problematic.Using CWE to declare the problem leads to CWE-197. Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
A vulnerability was found inSQLite upto 3.50.1. It has beenratedas problematic.Using CWE to declarethe problem leadstoCWE-197. Truncation errors occur when a primitive is castto a primitive of asmaller sizeand data is lost in the conversion.Impacted is confidentiality, integrity, and availability.Upgrading to version 3.50.2 eliminates this vulnerability.The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21441).
There exists a vulnerabilityin SQLiteversions before 3.50.2wherethe number of aggregate terms couldexceed the numberofcolumns available. This could lead to a memory corruptionissue. We recommendupgrading toversion 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue.
