LiveActive security incident?Get immediate response
CVE Record

CVE-2026-51300: A use-after-free vulnerability exists in the expression parsing and memory management logic of SQLite 3.41.

A use-after-free vulnerability exists in the expression parsing and memory management logic of SQLite 3.41. After invoking sqlite3ExprDelete to release an expression object, the program still retains the dangling pointer and subsequently accesses member fields of the already freed memory. By constructing malicious SQL queries, a remote attacker can trigger invalid memory access, leading to application crash and sensitive memory information leakage.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

SQLite 3.41 may access an expression object after freeing it when processing malicious SQL. An exposed application could crash or disclose sensitive memory. Business risk depends on whether the application uses the affected SQLite release and permits untrusted input to influence SQL queries.

Executive priority

Prioritize rapid exposure assessment because the claimed impact includes unauthenticated denial of service and memory disclosure. Escalate systems confirmed to combine SQLite 3.41 with attacker-influenced SQL. Avoid declaring an emergency patch campaign until authoritative affected-version and fixed-version guidance is available.

Technical view

The reported CWE-416 use-after-free occurs in SQLite expression parsing and memory management. After sqlite3ExprDelete releases an expression object, a dangling pointer reportedly remains and member fields are later accessed. The supplied CVSS 3.1 score is 9.1, reflecting remotely reachable, low-complexity crashes and confidentiality loss without privileges or user interaction.

Likely exposure

Potential exposure includes applications embedding SQLite 3.41 where remote, unauthenticated input can influence SQL processed by the database. The source bundle provides no confirmed affected version range, product inventory, CPEs, deployment conditions, or validated reachability details beyond SQLite 3.41.

Exploitation context

The bundle describes malicious SQL as the trigger but provides no evidence of exploitation in the wild. The CVE is not listed as KEV in the supplied data. Treat remote reachability as application-dependent because SQLite is typically embedded and may not receive attacker-controlled SQL directly.

Researcher notes

Evidence is incomplete. The bundle identifies SQLite 3.41 and expr.c but supplies no affected range, fixed commit, patched release, reproduction validation, or official SQLite advisory. The referenced repository source file alone does not establish vulnerable versions. Researchers should distinguish the reported condition from confirmed application-level reachability.

Mitigation direction

  • Inventory applications and dependencies containing SQLite 3.41.
  • Restrict untrusted input from controlling SQL query structure.
  • Use parameterized queries where application design permits.
  • Apply vendor-confirmed remediation when official guidance identifies a fixed release.
  • Monitor affected applications for crashes or abnormal memory-related behavior.

Validation and detection

  • Confirm the SQLite runtime version actually loaded by each application.
  • Trace whether unauthenticated input can influence SQL expressions or query structure.
  • Review crash reports and logs for failures during expression processing.
  • Verify compensating input controls and query parameterization are consistently enforced.
  • Reassess after SQLite publishes authoritative affected-version and remediation guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-51300 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-51300Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.