Latest

Technology

KeePassXC 2.8.0 jumps to Qt6 and debuts Auto-Type on Wayland

KeePassXC 2.8.0 was released on October 21, 2026 with Auto-Type on Wayland via XDG portals, a jump to Qt6, configurable shortcuts and remote synchronization.

KeePassXC 2.8.0 jumps to Qt6 and debuts Auto-Type on Wayland
KeePassXC 2.8.0 jumps to Qt6 and debuts Auto-Type on Wayland

If you use the KeePassXC password manager, Auto-Type was the feature most missed on Wayland. It consists of the password manager typing the username and password into the window in front of you without going through the clipboard, and on Linux it had been limited to X11 sessions for years. KeePassXC 2.8.0 has also enabled it on Wayland without bypassing the compositor: the global shortcut is delivered by the GlobalShortcuts portal and the keystrokes travel through the RemoteDesktop portal, according to the project's changelog.

The version was released on October 21, 2026, a month after the 2.8.0-beta1 beta of September 23 and more than seven months after the last stable release of the previous branch, 2.7.12 on March 10. Along with Auto-Type come the migration from Qt5 to Qt6, configurable shortcuts, remote synchronization with external tools and two new forms of quick unlock, one for macOS and one for Linux. It is also the first release with native ARM64 binaries for Windows.

For anyone maintaining the package in a distribution, the real headline is Qt6. The framework's 5.15 branch stopped receiving open releases with 5.15.2 in November 2020 and its commercial support ended on May 26, 2025, so every season on Qt5 was another season compiling against a frozen library.

Auto-Type on Wayland without leaving the compositor

Wayland's Auto-Type does not touch the keyboard directly. KeePassXC asks the desktop for a global shortcut and a remote desktop session through which to send keystrokes, and both are managed by XDG portals.

The shortcuts portal gives the application the combination that triggers the action, and the remote desktop portal opens the session through which the keystrokes are injected. There is no brute-force keyboard capture or reading of someone else's window: the desktop asks for control permission the first time, just as when you share your screen, and the application keeps the session token in memory to avoid repeating the dialog on every use.

The practical consequence is that Auto-Type by window title disappears. On Wayland no application can know which window has focus, so the project hid the options that tied sequences to specific titles. Now you press the shortcut, search for the entry in the dialog and the password is typed into the field in front of you, which works just as well but requires one more step than on X11.

Auto-Type was one of the reasons not to make the jump. The rest of the differences you will notice when migrating are in Wayland versus X11 in 2026, what changes when migrating, and with this piece resolved the list of brakes is considerably shorter.

The compatibility detail matters. The author of the patch tested the result on KDE Plasma 6.3 on Debian trixie, where everything works except reconfiguring the shortcut from KeePassXC because the shortcuts portal was on version 1, and on Plasma 6.6, where that reconfiguration already works. On GNOME 48 the initial binding works, but changing the combination from the desktop settings fails silently until the session is restarted.

That nuance is not cosmetic. Anyone who changes the shortcut from the desktop settings will think it has not been saved and will try again, even though the failure is on the desktop side. The first configuration almost never works on the first try.

Qt6 and the countdown Qt5 had been dragging along

The migration is not a number change in the manifest. KeePassXC 2.8.0 requires Qt 6.2.4 as a minimum and compiles with C++20, according to its CMakeLists, so the package is no longer built against the Qt5 tree that some older distributions drag along. The dependencies are no longer those of Qt5: the package now declares those of qt6-base and its modules.

The calendar explains the hurry. Qt 5.15 received its last open release with 5.15.2, from November 2020, and the following ones were only for commercial customers; support for that branch ended on May 26, 2025 and after that came paid extended security maintenance. Every month on Qt5 was a month with the graphics library frozen.

For the packager, the good news is that the Qt6 floor is not high: Debian 12 ships 6.4.2 and Debian 13 ships 6.8.2, so both cover the minimum. The bad news is that the build options have to be reviewed, because the project allows building without X11 and groups browser, SSH agent and Secret Service under one CMake switch. In addition, the state now lives in XDG_STATE_HOME and not in XDG_CACHE_HOME.

That last change is the one that breaks small things. Copy and cleanup scripts that took the old path for granted will no longer find the state file: the application will simply start writing to another directory.

What the version brings, in order of use

New feature What changes Platform
Auto-Type on Wayland Global shortcut and remote desktop via XDG portals Linux
Qt6 Minimum Qt 6.2.4 and C++20 All
Configurable shortcuts Any action can be reassigned; Ctrl+D clones entries All
Remote synchronization Opens, imports and saves the database with external commands All
Quick unlock Device password on macOS; Polkit on Linux macOS and Linux
ARM64 Native installer on Windows and experimental AArch64 AppImage Windows and Linux
Group policies Administrators enforce settings on each machine Windows
SSH agent Generates RSA, ECDSA and Ed25519 keys All

Remote synchronization is the new feature that most changes the day-to-day for those who keep the database on their own server. KeePassXC allows configuring external commands, one to open the database from the server and another to import or upload it when you save, so the file travels without you having to leave the manager. Anyone who already has a server at home will recognize the pattern of a self-hosted service, the same one we broke down in Self-hosting in 2026, what to set up and what not to, where file synchronization is the piece that causes the most trouble.

Polkit, the UUID and the price of convenience

Quick unlock via Polkit touches the file. When you enable it, KeePassXC adds a UUID to the database's public metadata and marks it as modified the first time it is opened, as the changelog warns. That identifier is what allows Polkit to recognize the database and save the master password in already authenticated sessions.

It is a reasonable trade-off, but it is worth understanding before enabling it. You gain convenience on the desktop and, in exchange, the file stops being indistinguishable from any other copy: anyone who sees the database will know there is a manager behind it and that it is tied to a specific session. In a database synchronized to the cloud, that UUID travels everywhere.

Five patches, one CVE and four pending identifiers

The release patches five vulnerabilities that affected the 2.7.x branch and all earlier ones. Only one has an assigned identifier, CVE-2026-69150, a use-after-free when importing manipulated KDB files; the other four are still marked as pending: reference injection from the browser extension, out-of-bounds writes when encrypting native messages, predictable shared memory names when sending SSH keys to Pageant and an overflow in the old KDB importer.

The project rates the flaws as low to moderate severity and clarifies that none compromises the cryptography. It adds a detail that has been recurring these months: they were found by AI scanners and none came from AI-generated code. More than a month after requesting it, GitHub has still not assigned CVE identifiers to most of them.

That bottleneck affects those who package: an advisory without a CVE does not enter the distributions' automated flows, so the update depends on someone reading the blog. For the user, all that remains is updating from Flathub, the Ubuntu PPA or the project's website.

What Auto-Type on Wayland still does not solve

There is a loose end that the patch thread documents. A user who tested three virtual input engines on Plasma 6.6 reported altered keystrokes with Auto-Type on Wayland, with modifiers that stayed pressed and characters different from those saved. The team responded that KeePassXC sends correct Unicode symbols derived from libxkbcommon and that the conversion fails in the portal or in the compositor, so there is no patch and the way out is your own script that invokes the shortcut via D-Bus.

The rest is desktop follow-up. When the shortcuts and remote desktop portals mature, the feature will behave the same on any compositor and will stop depending on the Plasma version or the GNOME patch. In the meantime, 2.8.0 is the first version with which someone on Wayland can type passwords with the usual shortcut.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading