CVE-2026-50812 json
A NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows…
published 2026-07-08 4 mo ago modified 2026-07-09 4 mo ago also EUVD-2026-42501
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
A NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows an attacker who can supply a malformed changeset blob to cause a denial of service. The issue occurs when sqlite3changeset_apply_v3() applies a corrupt changeset and reaches sqlite3_value_type() with a NULL sqlite3_value pointer.
Patch / fix
- sqlite3 Debian 14 3.53.2-1
debian advisories DEBIAN-CVE-2026-50812
- sqlite3 Ubuntu 22.04 LTS 3.37.2-2ubuntu0.7
- sqlite3 Ubuntu 24.04 LTS 3.45.1-1ubuntu2.7
- sqlite3 Ubuntu 26.04 LTS 3.46.1-9ubuntu0.2
ubuntu advisories UBUNTU-CVE-2026-50812
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- lemon hummingbird 1 3.53.3-1.hum1
- sqlite hummingbird 1 3.53.3-1.hum1
- sqlite-tcl hummingbird 1 3.53.3-1.hum1
- sqlite-libs hummingbird 1 3.53.3-1.hum1
- sqlite-tools hummingbird 1 3.53.3-1.hum1
- sqlite-analyzer hummingbird 1 3.53.3-1.hum1
red hat advisories RHSA-2026:39023
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-50812 updated cvss 5.5
sqlite: SQLite: Denial of Service via malformed changeset in Session Extension
-
Red Hat Enterprise Linux 8 lemon, sqlite, sqlite-libs, mingw-sqlite, mingw32-sqlite, mingw64-sqlite Red Hat Enterprise Linux 9 sqlite, sqlite-libs Red Hat Enterprise Linux 10 sqlite Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-core-bff-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-mod-arch-maas-rhel9, rhoai/odh-mod-arch-automl-rhel9, rhoai/odh-mod-arch-gen-ai-rhel9, rhoai/odh-mod-arch-mlflow-rhel9, +6 moreunder investigation
-
Red Hat Hardened Images lemon 3.53.3-1.hum1, sqlite 3.53.3-1.hum1, sqlite-tcl 3.53.3-1.hum1, sqlite-libs 3.53.3-1.hum1, sqlite-tools 3.53.3-1.hum1, sqlite-analyzer 3.53.3-1.hum1fixed: vendor fix RHSA-2026:39023
-
Red Hat Enterprise Linux 6 lemon, sqlite, sqlite-tcl Red Hat Enterprise Linux 7 lemon, sqlite, sqlite-tcl Red Hat Enterprise Linux 8 npm, rls, rust, cargo, clippy, nodejs, +15 more Red Hat Enterprise Linux 9 npm, rust, cargo, clippy, nodejs, rustfmt, +12 more Red Hat Enterprise Linux AI (RHEL AI) 3 rust Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-kube-rbac-proxy-rhel9, rhoai/odh-maas-controller-rhel9, rhoai/odh-mlflow-operator-rhel9, rhoai/odh-model-controller-rhel9, rhoai/odh-ogx-k8s-operator-rhel9, +14 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
Sources
- CVE List CVE-2026-50812
- NVD CVE-2026-50812
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.