KeePassXC 2.8.0 is the stable release. One import bug is named. The rest stay low.
KeePassXC 2.8.0, tagged October 21, moves to Qt 6. The project names CVE-2026-69150 on KDB import and says the other fixes are not core crypto.
The short version
KeePassXC 2.8.0 is the project's stable release, tagged October 21. It moves the interface to Qt 6. The project says every 2.7 release and earlier is affected by issues fixed here, names CVE-2026-69150 as a use-after-free when importing a crafted KDB file, and says the other fixes are not in the core crypto. It recommends updating.
The tag is the release
KeePassXC's October 21, 2026 post, from Janek Bevendorff, announces 2.8.0 as the stable release. The GitHub tag 2.8.0 points at commit 1c2f23e and was published the same day. LWN's item is the other account. The headline change is the move to Qt 6. A toolkit migration is a real release. It is not, by itself, the security note. Both belong in the record because the project shipped them together. Asked directly, Are the other fixes core crypto bugs? The project says they are not. It rates the browser, native-messaging, and Windows shared-memory issues fixed since the beta as low to moderate, and says GitHub had not assigned most of those CVEs.what a license obligates.
One identifier, one class of bug
The project names CVE-2026-69150 as a use-after-free when importing a crafted KDB file. That is the class. This page will not describe the file, the importer path, or a payload. Other fixes, in the browser integration, the native-messaging host, and Windows shared memory, were addressed in the beta. The project says GitHub had not assigned CVE identifiers to most of them, rates them low to moderate, and says they are not in the core cryptography. A missing CVE number is not a statement that the issue is imaginary. It is a statement about the tracker.
How the project says the bugs were found
KeePassXC says none of these issues were introduced by AI-generated code, and that AI assisted in finding them. That sentence is about the project's own history of this release. It is not a general claim about other password managers, and it is not a reason to skip the update. The recommendation in the post is to move off 2.7.x and earlier. The version is the whole of the action this brief will state. Asked directly, What changes for Wayland? The project says Auto-Type on Wayland goes through XDG portals. That is an input path, not a new database format.
What else the release notes change
On Linux, the project says Wayland Auto-Type goes through XDG portals, and Polkit Quick Unlock adds a UUID to the database's public metadata, marking the file modified on first launch. On macOS, Quick Unlock can use the device password. On Windows, Group Policy can override settings, and a native ARM64 build is available. An experimental AArch64 AppImage is named. Remote database sync is left to external tools. Shortcuts are configurable. The SSH agent can generate RSA, ECDSA, and Ed25519 keys. Those are feature notes, not the vulnerability.the key stays with the holder.
A UUID in public metadata is not the secret
The project is explicit that the Linux Quick Unlock UUID lands in public metadata. A database marked modified on first launch will look like a user edit to a sync tool. That is an operational surprise, not a disclosure of the passphrase. People who replicate the file should expect a one-time change. People who thought Quick Unlock stored the database key in that UUID are reading a field the project says is an identifier.
Who the update is for
Everyone on KeePassXC 2.7.x or older, which the project says is the affected range. Browser-integration users are inside the moderate issues even though those issues are not core crypto. People who only open a database and never import a KDB file are still inside the project's update recommendation, because the project did not split the release into an optional import patch. Distributions that have not packaged 2.8.0 yet are a packaging lag, not a reason the tag does not exist.a signature on a package.
Who is in scope
KeePassXC users and the packagers who ship it. A team that embedded an older KeePassXC build in an appliance is in scope for the version check. People who use a different password manager are not. The release does not say a cloud vault was breached. It says the desktop application has a new stable tag and a set of fixes. Asked directly, Does this page describe the KDB importer bug? No. The project calls CVE-2026-69150 a use-after-free when importing a crafted KDB file. The craft stays in the advisory.what a session cannot be.
What stays on the record
October 21, 2026. KeePassXC 2.8.0, tag commit 1c2f23e. Qt 6. Wayland Auto-Type via XDG portals. Linux Quick Unlock UUID in public metadata. macOS device-password Quick Unlock. Windows Group Policy and native ARM64. Experimental AArch64 AppImage. CVE-2026-69150 named as a use-after-free on crafted KDB import. Other fixes low to moderate, not core crypto, most without a CVE yet. All 2.7.x and earlier affected. Update recommended. AI did not write the bugs, on the project's account, and assisted in finding them.the advisory is the story.
What would move the row
A CVE assignment for the issues the project says are still unnumbered, or a 2.8 follow-up that corrects the import fix, would be a later document. A distribution package is a convenience, not a new finding. Until then the record is the project post, the tag, and LWN's account. The short answer this page will stand on is this: KeePassXC 2.8.0 is the project's stable release, tagged October 21. It moves the interface to Qt 6. The project says every 2.7 release and earlier is affected by issues fixed here, names CVE-2026-69150 as a use-after-free when importing a crafted KDB file, and says the other fixes are not in the core crypto. It recommends updating.what a CVE identifier is.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Does this page describe the KDB importer bug?
No. The project calls CVE-2026-69150 a use-after-free when importing a crafted KDB file. The craft stays in the advisory.
Are the other fixes core crypto bugs?
The project says they are not. It rates the browser, native-messaging, and Windows shared-memory issues fixed since the beta as low to moderate, and says GitHub had not assigned most of those CVEs.
What changes for Wayland?
The project says Auto-Type on Wayland goes through XDG portals. That is an input path, not a new database format.
What does Quick Unlock write on Linux?
The project says Polkit Quick Unlock adds a UUID to public metadata and marks the database modified on first launch. The UUID is an identifier, not the database key.
Who should update?
The project says all 2.7.x releases and earlier are affected and recommends moving to 2.8.0. A recommendation is the project's, and the version is the action.