Critical CVE issued for hallucinated SQLite vulnerability
A GitHub repository recently published a batch of SQLite vulnerability advisories, which were quickly flagged as critical by NVD and CISA's ADP. However, upon further investigation by JFrog security researchers, the claims were found to be false, with the cited code not existing in the specified versions or referencing unrelated logic. The advisories are believed to be AI-generated, highlighting concerns about the reliability of these CVEs and the potential for LLM slop in the vulnerability reporting process.
- ▪The GitHub repository published over 50 CVEs, which were initially flagged as critical by NVD and CISA's ADP.
- ▪JFrog security researchers found that the cited code did not exist in the specified versions or referenced unrelated logic, rendering the advisories false.
- ▪The advisories are believed to be AI-generated, with analysis showing that they triggered AI-generated content warnings when combined into one file.
2 outlets in our directory ran this story, first to last over 3 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ SQLite Critical CVEs or LLM Slop? (JFrog blog) — LWN.net (Linux Weekly News)
Hacker News (Front Page) files mainly under programming. We currently carry 1,027 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Jfrog |
| Canonical URL | https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/ |
| Publication time | Mon, 03 Aug 2026 11:28:54 +0000 |
| Retrieval time | 2026-08-03T11:45:45.951Z |
| Last seen | 2026-08-03T11:45:45.951Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | _Xz5NsqU9D2C · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
SQLite Critical CVEs or LLM Slop?Afek Berger, JFrog Security Researcher | 30 Jul, 2026 Over the past few days, a newly created GitHub repo (programmervuln/cveadvisory-) published a batch of SQLite vulnerability advisories (as part of other 50+ CVEs which we believe are also LLM slop except from one). NVD quickly flagged these as critical, and CISA's ADP agreed. But when JFrog security researchers dug in to verify, the claims fell apart: The cited code didn't even exist in those versions or referenced unrelated logic. When testing the PoC payloads they didn’t work (not triggering any crash). None of these CVEs are listed on SQLite’s official advisory page (which is a gold standard for tracking actual vulnerabilities).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Jfrog.
Discussion
0 commentsMore from Jfrog
