# CVE-2026-69150: KeePassXC: Heap use-after-free in KeePass1 (KDB) importer via unpruned m_entryUuids map

> A crafted KDB file triggers a heap use-after-free in KeePassXC, allowing attackers to cause a crash or potentially execute code.

- **Severity:** Medium 4.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-69150, GHSA-4642-49vv-4p43, UBUNTU-CVE-2026-69150

## What is CVE-2026-69150?

CVE-2026-69150 is a medium-severity use after free vulnerability in keepassxreboot keepassxc, published on 13 Oct 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

KeePassXC is a cross-platform community-driven port of the Windows application KeePass Password Safe. Prior to 2.8.0-beta1, KeePass1 / KDB legacy import retains raw Entry pointers in m_entryUuids after deleting metastream entries. When a crafted, unlockable .kdb file contains an earlier metastream entry followed by a KPX_CUSTOM_ICONS_4 metastream that references the earlier UUID, parseCustomIcons4() calls Entry::setIcon through the stale pointer, causing a heap use-after-free with a controlled write and a reliable process crash. This issue is fixed in version 2.8.0-beta1.

Weakness: CWE-416 (Use After Free)

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


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

No fix has been published for CVE-2026-69150 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-69150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69150 is a medium-severity use after free vulnerability in keepassxreboot keepassxc, published on 13 Oct 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-69150 in the wild and no public exploit code.

Affected product: keepassxreboot keepassxc. 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-69150/ (Markdown: https://insights.sbomify.com/CVE-2026-69150/index.md)
```

## Sources

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

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