SQLite Session Extension CVE-2026-50812

Exploitation requires three specific conditions: (1) the target SQLite build must have been compiled with SQLITE_ENABLE_SESSION - this is not the default for many embedded distributions; (2) the target application must invoke sqlite3changeset_apply_v3() on its data path; and (3) the attacker must have low-privilege local access sufficient to supply a malformed changeset blob to that application, either as a file, IPC argument, or API input. The CVSS PR:L metric confirms authentication or equivalent local access is required - unauthenticated remote exploitation is not indicated. What limits exploitation: the Session Extension is a non-default compile-time feature, the attack vector is local (AV:L), and impact is availability-only with no data exfiltration or code execution. Applications that process only internally generated, trusted changesets face no realistic risk even if the Session Extension is compiled in.

The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, score 5.5) accurately characterizes a local, low-privilege denial-of-service. The local attack vector is the primary limiting factor: an attacker must be able to supply malformed changeset data to an application that invokes sqlite3changeset_apply_v3(), which is not a default or universally exposed code path. Applications that only generate or consume internally trusted changesets are not realistically at risk. No EPSS score was provided and the vulnerability is not in CISA KEV, so there is no confirmed or probabilistic signal of active exploitation. The referenced public gist raises the POC flag slightly - exploit construction appears straightforward given the NULL dereference class - but this remains a DoS-only flaw with no confidentiality or integrity impact. Real-world priority should be low-to-medium: patch when the SQLite amalgamation is next updated, and immediately audit any application that feeds externally sourced changeset blobs into sqlite3changeset_apply_v3().

An attacker with low-privilege local access crafts a binary changeset blob containing corrupt data - sufficient to cause the SQLite iterator to produce a NULL sqlite3_value pointer - and supplies it to a target application that calls sqlite3changeset_apply_v3(), causing an immediate NULL pointer dereference and process crash. A public PoC gist is referenced at https://gist.github.com/junius-sec/bb556f333957c5226dede314db0e9e91, suggesting the crash is reproducible with a crafted input. The attack requires no special privileges beyond the ability to provide input to the application's changeset processing path.