PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-119376 SQLite CVE debrief

SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators, potentially causing a crash in sqlite3WalkExprNN(). This vulnerability can be triggered by supplying roughly 175,000 chained COLLATE operators in SQL or an untrusted database view, leading to unbounded recursion and a process crash. Defenders and developers using SQLite versions prior to 3.54.0 should assess exposure and prioritize verification and upgrades.

Vendor
SQLite
Product
Unknown
CVSS
MEDIUM 6.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-30
Original CVE updated
2026-11-02
Advisory published
2026-10-30
Advisory updated
2026-11-02

Who should care

Defenders and developers using SQLite versions prior to 3.54.0 should assess exposure and prioritize verification and upgrades. This includes reviewing systems that use SQLite, identifying potential vulnerabilities, and taking steps to mitigate them. Additionally, security teams and operators should be aware of the potential impacts of this vulnerability, including potential crashes or errors in SQLite applications, and take steps to monitor and detect any

Why it matters

Defenders should prioritize verifying and upgrading to SQLite version 3.54.0 or later to prevent potential crashes. Assess exposure in systems using SQLite versions prior to 3.54.0.

  • Potential crashes or errors in SQLite applications
  • Bypassing of SQLITE_LIMIT_EXPR_DEPTH limit
  • Unbounded recursion in sqlite3WalkExprNN()

Technical summary

The vulnerability allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators, potentially causing a crash in sqlite3WalkExprNN(). This can be achieved by supplying roughly 175,000 chained COLLATE operators in SQL or an untrusted database view, leading to unbounded recursion. The vulnerability affects SQLite versions before 3.54.0 and can be mitigated by upgrading to version 3.54.0 or later. Defenders should prioritize verifying and upgrading to prevent potential crashes and assess exposure in systems using SQLite versions prior to 3.54.0.

Defensive priority

Defenders should prioritize verifying and upgrading to SQLite version 3.54.0 or later to prevent potential crashes. Assess exposure in systems using SQLite versions prior to 3.54.0.

Recommended defensive actions

  • Verify SQLite version and upgrade to 3.54.0 or later if necessary
  • Assess exposure in systems using SQLite versions prior to 3.54.0
  • Monitor for potential crashes or errors in SQLite applications
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the stack exhaustion vulnerability in SQLite before version 3.54.0. The vulnerability allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators, potentially causing a crash.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-119376 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-119376

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-119376 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-119376

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.