SQLite 3.41 has a use-after-free vulnerability in the shared cache lock management logic of the btree module. The program frees a BtLock structure without removing the node from the linked list. Subsequent linked list traversal accesses the released memory, which can lead to denial of service and sensitive memory information disclosure.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-51290 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
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-51290
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Jul 30, 2026sqlite/src/btree.c at master · sqlite/sqlite · GitHub
https://github.com/sqlite/sqlite/blob/master/src/btree.ccveadvisory-/CVE-2026-51290md at main · programmervuln/cveadvisory- · GitHub
https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51290mdVendor Advisories for CVE-2026-51290(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 20:36 UTCGHSA enrichment
- 2026-08-17 02:51 UTCGHSA enrichment
- 2026-08-14 09:07 UTCGHSA enrichment
- 2026-08-11 15:23 UTCGHSA enrichment
- 2026-08-08 21:39 UTCGHSA enrichment
- 2026-08-06 03:54 UTCGHSA enrichment
- 2026-08-03 10:11 UTCEG score recompute
- 2026-08-03 10:11 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:27 UTCEG score recompute▼ 9.10
- 2026-07-31 16:27 UTCGHSA enrichment
- 2026-07-31 12:22 UTCGHSA enrichment
- 2026-07-31 08:24 UTCGHSA enrichment
- 2026-07-31 04:26 UTCGHSA enrichment
- 2026-07-31 00:29 UTCEG score recompute
- 2026-07-31 00:29 UTCGHSA enrichment
- 2026-07-30 20:33 UTCEG score recompute▲ 9.10
- 2026-07-30 20:32 UTCGHSA enrichment
- 2026-07-30 20:32 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
- 2026-07-30 19:34 UTCGHSA enrichment
- 2026-07-30 19:33 UTCNVD update
- 2026-07-30 19:31 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-07-30 17:23 UTCNVD update
- 2026-07-30 16:49 UTCEG score recompute
- 2026-07-30 16:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-51290?
When was CVE-2026-51290 disclosed?
Is CVE-2026-51290 actively exploited?
What is the CVSS score of CVE-2026-51290?
How do I remediate CVE-2026-51290?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51290
Is Your Infrastructure Affected by CVE-2026-51290?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.