CVE-2026-51297Disclosure

MEDIUM

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Patch affected systems immediately
  • Hunt for exploitation attempts and persistence artifacts
  • Increase monitoring for publicly documented tradecraft

Recommended action window: High priority (within 72h)

NVD description

Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

4.0/ 10 priority

Priority

MEDIUM

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Threat summary

  • Public PoC and exploit tooling are both present
  • Patch or workaround signal is available
  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Exploit tool or code specified in 1 signal
  • PoC mentioned or linked in 3 signals
  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • False Positive: 1 classified signal
  • Peaked 1d ago at 2 mentions (2026-07-27); latest day: 1
  • 3 total mentions across 2 days

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-07-27: 2Mentions · 2026-08-03: 1PoC Mentioned / Linked · 2026-07-27: 2PoC Mentioned / Linked · 2026-08-03: 1Exploit Tool / Code · 2026-07-27: 1Patch / Workaround · 2026-07-27: 1Technical Details · 2026-07-27: 207-2708-03
Signal classification2 categories
Disclosure
266.7%
False Positive
133.3%
Referenced assets1 URL
By indicator
Classification over time
DateTotalLabels
2026-07-272
Disclosure2
2026-08-031
False Positive1
Full discourse3 posts
  • yousukezan@yousukezan
    False Positive

    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/

    Post summary

    JFrog’s review of multiple SQLite CVEs found that the advisories were based on incorrect or nonexistent code, rendering the CVEs false positives and likely the result of AI‑generated misinformation.

    0111562.8K
    16.0K followersView on X
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨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.

    Post summary

    The post announces an unverified SQLite use‑after‑free vulnerability (CVE‑2026‑51303), notes a public PoC and suggests patching by updating SQLite, but does not confirm active exploitation or vendor support.

    00000145
    254 followersView on X
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨High - Reported SQLite JSON Parser Use-After-Free (CVE-2026-51297) A use-after-free is reported in SQLite 3.41's JSON parsing logic: a crafted JSON payload can free memory and then trigger an illegal access, potentially leading to code execution, information disclosure, or denial of service. CISA-ADP scored it 8.8 (network, no privileges, user interaction required) and notes a public PoC. Caveat: this is not vendor-confirmed. The only technical reference is an anonymous researcher's GitHub repo - there's no official SQLite advisory, no fix commit, and no patched version, and it fits the pattern of low-quality SQLite CVEs the project often disputes. Verify against the SQLite project before acting. 👉If you parse untrusted JSON via SQLite's JSON functions on an old 3.41-era build, monitor for an official SQLite fix and update to a current release; otherwise treat as unverified pending confirmation.

    Post summary

    A use‑after‑free vulnerability in SQLite 3.41’s JSON parser (CVE‑2026‑51297) has been publicly disclosed with a PoC, but no vendor confirmation or patch exists and no active exploitation has been reported.

    00000101
    254 followersView on X

Explore more