# CVE-2026-50812: Null dereference in n/a

> An attacker can cause a denial of service in SQLite by supplying a malformed changeset blob that triggers a NULL pointer dereference.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** BELL-CVE-2026-50812, DEBIAN-CVE-2026-50812, ECHO-f08c-2b40-760b, GHSA-f8h2-hw8x-2jh9, OESA-2026-3492, OESA-2026-3493, OESA-2026-3494, OESA-2026-3495, RHSA-2026:39023, UBUNTU-CVE-2026-50812

## What is CVE-2026-50812?

CVE-2026-50812 is a medium-severity vulnerability in n/a, published on 8 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-50812?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lemon` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-analyzer` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-debug` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-devel` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-doc` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-libs` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-tcl` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |
| `sqlite-tools` | Red Hat:hummingbird:1 | All versions | 0:3.53.3-1.hum1 |

## How do I fix CVE-2026-50812?

Apply the vendor's patch.

## Is CVE-2026-50812 being exploited?

There is no known exploitation of CVE-2026-50812 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50812 and fix it if it is affected.

What it is: CVE-2026-50812 is a medium-severity vulnerability in n/a, published on 8 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50812 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50812/ (Markdown: https://insights.sbomify.com/CVE-2026-50812/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50812
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50812
- OSV: https://osv.dev/vulnerability/CVE-2026-50812

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50812/
Summaries are generated and may contain mistakes; the official description above is the record.