Skip to main content
Vulnerability Database/CVE-2026-69150

CVE-2026-69150: KeePassXC Use-After-Free Vulnerability

CVE-2026-69150 is a use-after-free vulnerability in KeePassXC that occurs during KeePass1 legacy import, allowing heap corruption through crafted files. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-69150 Overview

CVE-2026-69150 is a heap use-after-free vulnerability in KeePassXC, a cross-platform community-driven port of the KeePass Password Safe application. The flaw resides in the legacy KeePass1 (.kdb) import routine. Prior to version 2.8.0-beta1, the importer retains raw Entry* pointers in m_entryUuids after deleting metastream entries. A crafted .kdb file containing an early metastream entry followed by a KPX_CUSTOM_ICONS_4 metastream that references the earlier UUID forces parseCustomIcons4() to call Entry::setIcon through a stale pointer. This triggers a controlled write into freed heap memory and a reliable process crash.

Critical Impact

An attacker who convinces a local user to open a malicious .kdb file can trigger a heap use-after-free with a controlled write, crashing KeePassXC and potentially enabling further memory corruption.

Affected Products

  • KeePassXC password manager, all versions prior to 2.8.0-beta1
  • KeePass1 / KDB legacy import functionality
  • Cross-platform builds for Windows, macOS, and Linux

Discovery Timeline

  • 2026-10-13 - CVE-2026-69150 published to the National Vulnerability Database
  • 2026-10-13 - Last updated in NVD database
  • 2026-10-13 - GitHub Security Advisory GHSA-4642-49vv-4p43 published
  • Fixed in release - KeePassXC 2.8.0-beta1

Technical Details for CVE-2026-69150

Vulnerability Analysis

The vulnerability is a classic use-after-free [CWE-416] in src/format/KeePass1Reader.cpp. During KDB import, KeePassXC iterates over parsed entries and treats metastream entries as container records for configuration data such as custom icons. When the parser encounters a metastream entry, it calls parseMetaStream(entry) and then deletes the Entry object. However, the entry's pointer remained registered in the m_entryUuids lookup table, leaving a dangling reference.

If a later KPX_CUSTOM_ICONS_4 metastream block contains a UUID that resolves back to the freed entry, parseCustomIcons4() retrieves the stale pointer and invokes Entry::setIcon. The write occurs against reclaimed heap memory, giving an attacker partial control over data written to freed storage.

Root Cause

The root cause is incomplete bookkeeping during object destruction. m_entryUuids and m_entryGroupIds were not pruned when metastream entries were deleted, violating the invariant that the lookup tables mirror live Entry objects. Subsequent dereference of the stale pointer produces the use-after-free condition.

Attack Vector

Exploitation requires local user interaction. The victim must open a crafted, unlockable .kdb file through the KeePass1 import path. Successful parsing invokes the vulnerable code path and triggers the stale write, producing a reliable crash and heap corruption suitable for further exploitation research.

cpp
// Patch excerpt from src/format/KeePass1Reader.cpp
     for (Entry* entry : asConst(entries)) {
         if (isMetaStream(entry)) {
             parseMetaStream(entry);
-
+            m_entryUuids.remove(m_entryUuids.key(entry));
+            m_entryGroupIds.remove(entry);
             delete entry;
         } else {
             quint32 groupId = m_entryGroupIds.value(entry);

Source: KeePassXC commit 6a534f3. The fix removes the deleted entry from both lookup maps before delete entry, eliminating the dangling pointer.

Detection Methods for CVE-2026-69150

Indicators of Compromise

  • Unexpected crashes of keepassxc or keepassxc-cli immediately after a user initiates a KeePass1 / .kdb import.
  • Presence of unsolicited .kdb files delivered via email, chat, or shared drives, especially from untrusted sources.
  • Crash dumps showing faults inside KeePass1Reader::parseCustomIcons4 or Entry::setIcon on freed heap addresses.

Detection Strategies

  • Monitor endpoint telemetry for abnormal termination of KeePassXC processes correlated with recent file-open events on .kdb artifacts.
  • Hunt for .kdb files written to user profile directories by browsers, mail clients, or messaging apps on hosts running KeePassXC.
  • Enable AddressSanitizer or equivalent heap instrumentation in test environments to flag use-after-free conditions during KDB parsing.

Monitoring Recommendations

  • Inventory installed KeePassXC versions across managed endpoints and alert on any build older than 2.8.0-beta1.
  • Collect application crash reports centrally and correlate with file access events for .kdb imports.
  • Track outbound retrieval of .kdb attachments through email and web proxy logs.

How to Mitigate CVE-2026-69150

Immediate Actions Required

  • Upgrade KeePassXC to 2.8.0-beta1 or later on all endpoints using the KeePass1 import feature.
  • Advise users to avoid importing .kdb files from untrusted or unverified sources.
  • Restrict delivery of .kdb attachments at the email gateway until patching completes.

Patch Information

The issue is resolved in KeePassXC 2.8.0-beta1. The patch in commit 6a534f3 removes deleted entries from m_entryUuids and m_entryGroupIds before freeing them. Full technical details are documented in GitHub Security Advisory GHSA-4642-49vv-4p43.

Workarounds

  • Do not import legacy KeePass1 .kdb files; migrate password databases using a trusted system already running the patched version.
  • Block or quarantine .kdb files at mail and web gateways for users on unpatched builds.
  • Enforce application allowlisting to prevent execution of unpatched KeePassXC versions in high-risk environments.
bash
# Verify installed KeePassXC version and upgrade if below 2.8.0-beta1
keepassxc --version

# Example upgrade on Debian/Ubuntu after the fixed package is published
sudo apt update && sudo apt install --only-upgrade keepassxc

# Example upgrade on macOS via Homebrew
brew upgrade --cask keepassxc

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.