CVE-2026-51303General

NVDやCISA ADPが深刻度付きで登録したSQLiteの複数のCVEについて、JFrogが検証した結果、根拠となるアドバイザリの内容に多数の不整合が見つかり、生成AIによる誤情報である可能性が浮上した。実際のソースコードやPoCを検証しても脆弱性は再現できず、CVE情報の信頼性に疑問が投げかけられている。 問題となったのはGitHub上に新規作成された「programmervuln/cveadvisory-」リポジトリで公開されたSQLiteを含む50件以上のCVEアドバイザリである。NVDはこれらを重大な脆弱性として登録し、CISA ADPも評価したが、JFrogの調査ではアドバイザリが存在しない関数を引用していたり、対象バージョンに存在しないコードを根拠としていたり、無関係な処理を脆弱性として説明している例が確認された。PoCを公式SQLiteソースからビルドした環境でAddressSanitizerを用いて実行してもクラッシュは再現せず、SQLite公式の脆弱性一覧にも掲載されていなかった。また、アドバイザリ全体をGPTZeroで解析したところ、AI生成コンテンツと判定される結果になったという。対象にはCVE-2026-51302、CVE-2026-51303、CVE-2026-51300、CVE-2026-51297、CVE-2026-51296、CVE-2026-51304などが含まれ、存在しない関数や誤った修正内容、無関係なコード行などが記載されていた。さらにCVE-2026-51302は、当初CVSS 10.0として登録された後、7.6へ引き下げられていることも確認された。 https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/

CVE-2026-51302 and CVE-2026-51303 both scored CVSS 9.8 "Critical" against SQLite. Both are fake. AI-generated garbage. I pulled the SQLite source to check, and here is what I found. JFrog Security Research looked at 55 SQLite advisories filed from one GitHub account (programmervuln). 54 were completely fabricated. Only 1 had a real bug, and even that one was wrapped in unverified metadata. The tells were not subtle once you dig: The advisories named specific versions: 3.41.0, 3.51.2, 3.51.3. The vulnerable functions they cited did not exist in those versions. The proof-of-concept code crashed nothing. GptZero flagged the write-ups as AI-generated text. And these still got a 9.8 and flowed into the GitHub Advisory Database, NVD, and Red Hat feeds before anyone validated them. Think about what that means for a second. The attack is not against SQLite. SQLite was fine the whole time. The attack is against the vulnerability-management pipeline itself. Here is the part that should bother you if you automate anything. Building a security tool that ingests CVE feeds? A dependency scanner, an auto-patch bot, an agent that opens tickets when a Critical drops? BEFORE (dangerous): new CVE lands with CVSS 9.8 // bot trusts the score // auto-creates P0 ticket, pages on-call, maybe force-bumps the dependency // 3am fire drill over a function that does not exist AFTER (safe): new CVE lands with CVSS 9.8 // treat score + advisory text as UNTRUSTED input, same as user input // check: does the cited function exist in the named version? // check: does the PoC actually reproduce? // check: did a real maintainer confirm, or just a fresh throwaway account? // only then page a human The score is not evidence. The advisory text is not evidence. Reproduction is evidence. We spent years teaching people that LLM output is untrusted input. Turns out CVE feeds are now LLM output too. report-to-cleanup lag here was days, not months, which is the one bright spot. GitHub, Red Hat and NVD have flagged or removed them. But the next batch is already being written by a model somewhere. So here is my real question: how much of your patch pipeline runs on a CVSS number alone, with zero reproduction check? And when the fake CVE targets a library you actually ship, will your bot know the difference? #AISecurity #CVE #LLM

🟥 CVE-2026-51303 | SQLite, CVSS: 9.8 (Critical) a memory management flaw in the core parsing component. attackers can exploit this issue by supplying specially crafted SQL queries an attacker can trigger the issue remotely without needing any privileges or user interaction successful attacks can cause application crashes, data leaks, or code execution https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51303

SQLite 3.41: multiple vulnerabilities fixed URL: https://nvd.nist.gov/vuln/detail/CVE-2026-51303 Classification: Critical, Solution: Not Defined, Exploit Maturity: Unproven, CVSSv3.1: 9.8

🛡️ ExploitGrid Daily Threat Digest Top Vulnerabilities (CVEs) of the day CVE-2026-11756 CVE-2026-16812 CVE-2026-48030 CVE-2026-15014 CVE-2026-51303 ..🧵👇

[CVE] CVE-2026-51303 [HIGH PRIORITY] 🔗 https://exploitgrid.net/cve/CVE-2026-51303

CWE-416: Use After Free #EUVD: https://euvd.enisa.europa.eu/vulnerability/CVE-2026-51303 #NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-51303

🚨Critical (unverified) - Reported SQLite Parser Use-After-Free in ExprList (CVE-2026-51303) A use-after-free is reported in SQLite 3.41's core SQL parser: an ExprList object freed by sqlite3ExprListDelete is later accessed as a dangling pointer, so crafted SQL parsed by the engine could trigger the UAF - claimed to allow crash/DoS, memory disclosure, or in some cases code execution. CISA-ADP scored it 9.8 with a public PoC. Caveat: this is not vendor-confirmed. It's from the same anonymous researcher repo as CVE-2026-51297, isn't listed on SQLite's official CVE page, has no fix commit or patched version, and rests on the attacker being able to run arbitrary SQL - which SQLite's own policy treats as an application SQL-injection issue, not a new SQLite vulnerability. Realistic worst case is usually DoS, not reliable RCE. 👉Run a current SQLite (3.53.2+) as hygiene and don't feed untrusted SQL to the parser; don't treat this as an emergency until the SQLite project confirms it.