CVE-2026-69150
Received Received - Intake

Heap Use-After-Free in KeePassXC Prior to 2.8.0-beta1

Publication date: 2026-10-13

Last updated on: 2026-10-13

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-13
Last Modified
2026-10-13
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
CVE-2026-69150
EUVD
EUVD-2026-98810

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
keepassxreboot keepassxc < 2.8.0-beta1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-69150 is a use-after-free vulnerability in KeePassXC's KeePass1 (KDB) legacy import feature. When importing a crafted .kdb file, metastream entries are deleted without removing their UUIDs from a tracking map. A later metastream entry can then reference a freed entry's UUID, causing a use-after-free when Entry::setIcon() is called. This leads to a process crash and potential memory corruption.

Detection Guidance

Detecting this vulnerability requires checking the KeePassXC version installed on your system. Use the command 'keepassxc --version' to verify if your version is below 2.8.0-beta1. If it is, the system is vulnerable.

Impact Analysis

This vulnerability allows an attacker to crash the KeePassXC application by opening a specially crafted .kdb file. While full code execution wasn't demonstrated, the controlled write primitive could enable further memory corruption. The attack requires minimal user interaction (opening the file) and no special privileges.

Mitigation Strategies

Upgrade KeePassXC to version 2.8.0-beta1 or later immediately. Avoid importing untrusted KDB files until the update is applied. Monitor for crashes during KeePassXC operations as a potential sign of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-69150. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart