# CVE-2026-50813: Information disclosure in n/a

> A local attacker can obtain sensitive information via the Session Extension changeset merge path in SQLite.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:L/A:H/C:L/I:N/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** BELL-CVE-2026-50813, DEBIAN-CVE-2026-50813, ECHO-8734-f225-dcf5, GHSA-pp2q-fpvv-vr5h, OESA-2026-3490, RHSA-2026:23423, UBUNTU-CVE-2026-50813

## What is CVE-2026-50813?

CVE-2026-50813 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, and only if a user opens a file or follows a link.

### Official description

An issue in SQLite before Fossil check-in 869a51ae84df allows a local attacker to obtain sensitive information via the Session Extension changeset concat/changegroup merge path

Weakness: CWE-126 (Buffer Over-read)

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


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

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

Apply the vendor's patch.

## Is CVE-2026-50813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50813 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-50813 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-50813/ (Markdown: https://insights.sbomify.com/CVE-2026-50813/index.md)
```

## Sources

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

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