Fedora 45 Beta became available for public testing on September 15, 2026. It is a substantial platform transition: Fedora Workstation moves to GNOME 51, the kernel advances to Linux 7.2, and several security defaults change underneath package management, debugging and credential storage. Developers and system administrators also face a sizeable round of compatibility-sensitive updates.
Fedora 45 Beta is available for testing
Fedora 45 Beta is downloadable in Workstation, KDE Plasma Desktop, Server, Cloud and IoT editions, alongside Atomic Desktop, Spin and Lab images. Fedora's schedule lists October 20, 2026 as the first target for the final release and October 27 as the contingency target.
The beta installer itself labels Fedora Linux 45 Workstation Edition as a preliminary build while it configures storage, installs software and completes system setup.
The security defaults that change everyday administration
The clearest shift is in RPM package handling. Fedora 45 enforces signature verification by default, so RPM rejects packages whose signatures cannot be verified. That applies to downloaded packages and locally built unsigned RPMs; administrators can explicitly override the check with --nosignature or the corresponding API.
The default ptrace policy also restricts some debugging operations for unprivileged users. ptrace is the mechanism that lets debugging tools inspect or control another process. Installing debugging tools can restore the traditional behavior through a sysctl configuration, which keeps the stricter baseline while preserving a documented route for development work.
Credential storage moves to oo7, a Rust-based Secret Service provider that implements org.freedesktop.secrets over D-Bus. It replaces the environment-specific GNOME Keyring and KWallet defaults described in Fedora's change proposal. The design includes more consistent secret management across desktop environments; per-application authorization and FIDO2 support are described as planned capabilities rather than shipped security outcomes.
Fedora 45 also adds PAM support to chpasswd and newusers, allowing those utilities to follow system password rules such as complexity, history and auditing. DNF5 disables vendor changes by default, reducing automatic replacement of an installed package by another vendor's package unless the user takes an explicit action.
The platform stack moves forward
Fedora Workstation 45 Beta uses GNOME 51, while the dedicated Fedora KDE Plasma Desktop edition uses KDE Plasma 6.7. GNOME 51 includes a new fingerprint-management interface, SVG cursors, additional touchpad settings and multi-user remote login through Kerberos. Its Wayland background-effects protocol also enables applications and themes to implement responsive effects such as background blur where supported.
The beta includes Linux 7.2, with Cache Aware Scheduling and hardware-support changes including initial HDMI 2.1 FRL support in AMDGPU and USB4STREAM support associated with Intel hardware. Those kernel changes do not amount to a universal Fedora 45 performance result.
KMSCON replaces the legacy in-kernel virtual console for new Fedora 45 installations. That affects the text-based TTY reached through shortcuts such as Ctrl+Alt+F3; it does not replace graphical terminal applications such as Ptyxis, Konsole or Kitty.
Atomic Desktop images move to image-builder, and Fedora adds initial Anaconda WebUI installation flows together with remote WebUI installation support for Atomic Desktops.
Fedora 45 Beta: changes with the clearest reader impact
| Area | Fedora 45 Beta | Earlier behavior or series | Reader consequence |
| RPM signatures | Signature checking enforced by default, with an explicit override | Verification did not use this enforcing default | Unsigned or unverifiable packages require an intentional exception |
| Process debugging | Some unprivileged ptrace operations restricted by default | Traditional behavior can be restored through debugging-tool configuration | Debuggers and inspection tools may need an administrator-approved setup |
| Secret Service | oo7 becomes the default provider | GNOME Keyring and KWallet served as environment-specific backends | Credential storage gets a common desktop-oriented backend |
| Virtual console | KMSCON replaces the legacy in-kernel console | Legacy in-kernel virtual console | The TTY layer changes without replacing graphical terminal apps |
| MySQL default stream | MySQL 9.7 | MySQL 8.4 | Database administrators should review version-sensitive deployments |
| MariaDB default stream | MariaDB 12.3 | MariaDB 11.8 | Existing database workflows may require compatibility checks |
Where compatibility work is likely to surface
The largest upgrade risks are concentrated in developer tools, libraries and container infrastructure rather than in Fedora's desktop branding.
- Podman 6 introduces API and command-line breaking changes and removes slirp4netns, cgroups v1 and the BoltDB backend.
- Setuptools 82 removes pkg_resources.
- Pandas 3.0 moves beyond the 2.3 series.
- libxml2 2.15.3 includes an ABI change.
- The GNU toolchain advances to GCC 16.2, binutils 2.47, glibc 2.44 and GDB 17.2. Other notable updates include LLVM 23, Go 1.27, Python 3.15, Perl 5.44 and Lua 5.5.
- NetworkManager enables IPv6-mostly support by default.
For a workstation user, these changes may stay mostly beneath the surface. For anyone maintaining Python environments, database services, container stacks or native software, the version jumps deserve a review before upgrading production systems.
What beta testers should keep in mind
Users have reported failed Fedora 45 Beta live-image boots through Ventoy, KDE and SDDM display problems, multi-monitor issues, Wayland application trouble and recurring suspend failures involving input devices, session restoration and graphics. Those reports make the beta a better fit for a test machine or a backed-up system than for an installation that cannot tolerate surprises.
Fedora provides an offline upgrade path between releases, and users have reported upgrading from Fedora 44. A backup remains advisable before attempting a beta upgrade, particularly on systems that rely on third-party packages, custom graphics setups or container tooling.
