SQLite Critical CVEs or LLM Slop?
9 hours ago
- A GitHub repo published multiple SQLite vulnerability advisories that were quickly flagged as critical by NVD and CISA, but JFrog researchers found them to be AI-generated and false.
- The advisories cited non-existent code, referenced functions that didn't exist in the claimed versions, and provided PoCs that failed to trigger any crashes.
- None of the CVEs appeared on SQLite's official advisory page, and AI detection tools flagged the content as machine-generated.
- Red Hat initially assigned a 10.0 critical score to CVE-2026-51302 but later downgraded it to 7.6 high after further review.
- The CVE submission process lacks identity verification, and the NVD's pause on deep analysis in February 2024 has allowed fabricated advisories to enter databases.
- An audit of 55 advisories from the same account found 54 completely fabricated and one real but with unverified metadata.
- These fake CVEs waste organizational resources, pollute vulnerability databases, and can mislead AI-driven triage tools into generating unnecessary patches.
- Recommendations include verifying CVEs with official sources, investigating critical scores, checking affected environments, and reproducing PoCs in safe environments.