KeePassXC · Disclosed

KeePassXC 2.8.0 fixes use-after-free in legacy KDB import

· 1 min read

KeePassXC released version 2.8.0 with security fixes, according to DarkWebInformer. The update fixes CVE-2026-69150, a use-after-free triggered when importing a crafted legacy KDB file, plus browser, memory safety, and Windows issues still awaiting CVE assignments. Sources report no exploitation; update to 2.8.0.

WhatsApp LinkedIn X
HighVulnerabilityDisclosedPatched
In this article
  1. What happened
  2. Why it matters
  3. What to do
  4. For the technical team
  5. Timeline
  6. Sources

What happened

KeePassXC released version 2.8.0 on 2026-10-26 with several security fixes, according to DarkWebInformer. The main one fixes CVE-2026-69150, a use-after-free triggered when importing a crafted legacy KDB file. Other browser, memory safety, and Windows flaws are still awaiting CVE assignments.

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Why it matters

KeePassXC stores all of a company's passwords in one place. A malicious vault file sent to an employee, once imported, could crash or compromise that person's password manager. Any user who imports legacy KDB files from untrusted sources is exposed.

What to do

Update KeePassXC to version 2.8.0 on all workstations. Until then, instruct users not to import legacy KDB files received from third parties.

For the technical team

CVE
CVE-2026-69150
Affected
KeePassXC (gerenciador de senhas) · KeePassXC versions prior to 2.8.0; users importing crafted legacy KDB files.
Exploitation
No exploitation reported in the sources. Fix disclosed on 2026-10-26 by DarkWebInformer; additional flaws still awaiting CVE assignments.
Fix
Update to KeePassXC 2.8.0. Partial mitigation: do not import legacy KDB files from untrusted sources.
Vector
Legacy KDB importer: use-after-free triggered when importing a crafted legacy KDB file; the same importer also has an integer overflow and an out-of-bounds read. Requires the user to import the file. Other fixed flaws: browser entry reference injection, out-of-bounds writes in native messaging, weak Pageant shared-memory mapping names on Windows, and insufficient clearing of decrypted database fragments from memory.
More details
Release 2.8.0 also migrates to Qt 6 and adds remote database synchronization, configurable shortcuts, SSH key generation, Wayland Auto-Type, Linux Quick Unlock, and native Windows Arm64 builds. Single source: DarkWebInformer post on X.

Timeline

  1. Release 2.8.0 ships security fixes and moves to Qt 6.

Sources 1 source

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how. After signing up you get the full feed.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click