CVE-2026-51302
criticalrejectedpriority · track · 0EUNLRUUSRejected reason: 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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.5–10
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- NCSC-2026-0268Kwetsbaarheid verholpen in SQLite door SQLite Consortium (ingetrokken)NL2026-07-29csaf · ncsc_nlNL
~~SQLite Consortium heeft een kwetsbaarheid verholpen in SQLite versie 3.41.~~ **UPDATE** CVE is ingetrokken, de "kwetsbaarheid" is zeer waarschijnlijk door een LLM gehallucineerd. Zie bijgevoegde bron voor meer informatie.
- BIT-sqlite-2026-513022026-07-30vendor · osvUS
SQLite 3.41 has a use-after-free vulnerability exists in the expression evaluation logic. The sqlite3ReleaseTempReg function improperly releases temporary register resources, and the subsequent exprComputeOperands function continues to access the already freed register memory. By supplying a malicious SQL statement, a remote attacker can exploit this flaw to cause denial of service, leak sensitive information, or potentially execute arbitrary code on the affected system.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (3) cnnvd
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan