CVE-2026-51297

✕ Withdrawn — historical dataHIGHPre-NVD 8.8Elevated
8.8CVSS
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

sqlite 3.41 has a use-after-free vulnerability in the JSON parsing logic. Remote adversaries can craft malicious JSON payload to trigger memory free followed by illegal memory access, which may lead to arbitrary code execution, sensitive information leakage and service denial.

CVSS v3
8.8
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 27, 2026

Last Modified

July 29, 2026

Advisory Details (2)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

cveadvisory-/CVE-2026-51297 at main · programmervuln/cveadvisory- · GitHub

https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51297
generic

sqlite/src/json.c at master · sqlite/sqlite · GitHub

https://github.com/sqlite/sqlite/blob/master/src/json.c

Vendor Advisories for CVE-2026-51297(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsqlite-main-3.53.4-0.1.hum12026-07-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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.

  1. 2026-08-29 23:58 UTCVendor advisory
  2. 2026-08-29 23:58 UTCGHSA enrichment
  3. 2026-08-25 23:52 UTCVendor advisory
  4. 2026-08-25 23:52 UTCGHSA enrichment
  5. 2026-08-23 05:00 UTCVendor advisory
  6. 2026-08-23 05:00 UTCGHSA enrichment
  7. 2026-08-20 10:06 UTCVendor advisory
  8. 2026-08-20 10:06 UTCGHSA enrichment
  9. 2026-08-17 15:13 UTCVendor advisory
  10. 2026-08-17 15:13 UTCGHSA enrichment
  11. 2026-08-14 20:20 UTCVendor advisory
  12. 2026-08-14 20:20 UTCGHSA enrichment
  13. 2026-08-12 01:27 UTCVendor advisory
  14. 2026-08-12 01:27 UTCGHSA enrichment
  15. 2026-08-09 06:34 UTCVendor advisory
  16. 2026-08-09 06:34 UTCGHSA enrichment
  17. 2026-08-06 11:41 UTCVendor advisory
  18. 2026-08-06 11:41 UTCGHSA enrichment
  19. 2026-08-03 16:45 UTCVendor advisory
  20. 2026-08-03 16:45 UTCGHSA enrichment
  21. 2026-08-01 04:16 UTCEPSS rescore
  22. 2026-07-31 21:51 UTCEG score recompute 8.80
  23. 2026-07-31 21:51 UTCVendor advisory
  24. 2026-07-31 21:51 UTCGHSA enrichment
  25. 2026-07-31 09:26 UTCVendor advisory
Show 24 more
  1. 2026-07-31 09:26 UTCGHSA enrichment
  2. 2026-07-30 21:01 UTCEG score recompute
  3. 2026-07-30 21:01 UTCVendor advisory
  4. 2026-07-30 21:01 UTCGHSA enrichment
  5. 2026-07-30 16:28 UTCEPSS rescore
  6. 2026-07-30 08:36 UTCEG score recompute
  7. 2026-07-30 08:36 UTCGHSA enrichment
  8. 2026-07-30 01:30 UTCEPSS rescore
  9. 2026-07-29 20:11 UTCGHSA enrichment
  10. 2026-07-29 17:35 UTCGHSA enrichment
  11. 2026-07-29 05:09 UTCGHSA enrichment
  12. 2026-07-28 16:45 UTCEG score recompute
  13. 2026-07-28 16:45 UTCGHSA enrichment
  14. 2026-07-28 15:37 UTCEPSS rescore
  15. 2026-07-28 07:58 UTCEG score recompute
  16. 2026-07-28 07:57 UTCGHSA enrichment
  17. 2026-07-27 19:32 UTCEG score recompute
  18. 2026-07-27 19:32 UTCGHSA enrichment
  19. 2026-07-27 18:50 UTCEG score recompute 8.80
  20. 2026-07-27 18:50 UTCGHSA enrichment
  21. 2026-07-27 18:49 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  22. 2026-07-27 16:24 UTCNVD update
  23. 2026-07-27 15:31 UTCEG score recompute
  24. 2026-07-27 15:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-51297?
CVE-2026-51297 is a high vulnerability published on July 27, 2026. sqlite 3.41 has a use-after-free vulnerability in the JSON parsing logic. Remote adversaries can craft malicious JSON payload to trigger memory free followed by illegal memory access, which may lead to arbitrary code execution, sensitive information leakage and service denial.
When was CVE-2026-51297 disclosed?
CVE-2026-51297 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-51297 actively exploited?
CVE-2026-51297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.9% of all scored CVEs.
What is the CVSS score of CVE-2026-51297?
CVE-2026-51297 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-51297?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-51297, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-51297

Explore →

Is Your Infrastructure Affected by CVE-2026-51297?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.