AI-Generated Fake CVEs Mislead SQLite Security Reports

AI-Generated Fake CVEs Mislead SQLite Security Reports

First seen 4 Aug 2026, 02:19 UTC TheregisterXenospectrumFeeds.4Sysopswww2.sqlite.orgCybernews+6 87% similarity 36.1

Article Content

Browse articles
ThreatCluster

Six CVEs related to SQLite, published on July 27, 2026, were retracted just four days later after being found to be fabricated. The vulnerabilities, which included claims of use-after-free conditions, were assigned CVSS scores between 7.5 and 9.8 by CISA. JFrog tested the affected SQLite versions and found that none of the reported vulnerabilities were reproducible, leading to MITRE rejecting the CVEs on July 31. This incident highlights vulnerabilities in the CVE pipeline, particularly the ease with which AI-generated reports can be submitted and accepted. The SQLite developers confirmed that the reported issues were not legitimate bugs. The situation raises concerns about the reliability of automated security tools that rely on CVE databases. The incident serves as a cautionary tale for the cybersecurity community regarding the verification of vulnerability reports.

Key Points: • Six SQLite CVEs published in July 2026 were found to be fabricated and retracted. • CISA initially assigned high CVSS scores to the fake vulnerabilities, misleading security tools. • JFrog's testing revealed no reproducible vulnerabilities, prompting MITRE to reject the CVEs.

ThreatCluster AI How this analysis works

Timeline

2026-07-27
CVE-2026-51303 and CVE-2026-51300 published
MITRE published six CVEs for SQLite, claiming use-after-free vulnerabilities with high CVSS scores.
Xenospectrum
2026-07-31
MITRE rejects six SQLite CVEs
All six CVEs were marked as rejected after investigation determined they were not security issues.
Xenospectrum
2026-08-03
JFrog tests SQLite CVEs
JFrog found that none of the six SQLite CVEs were reproducible, confirming they were fabricated.
Theregister
2026-08-04
SQLite developers confirm CVEs are not legitimate
The SQLite development team stated that the reported vulnerabilities were not real bugs.
Feeds.4Sysops

Community

Browse all →