Fedora 45 delayed to November 3 over eMudhra certificate blocker
Fedora 45 has been pushed to 3 November while the project works through four blockers, including compromised eMudhra certificate keys.
Fedora 45 is no longer heading for its previously expected release window: the Fedora community has pushed the final release to 3 November while it works through four accepted blockers, including the fallout from compromised eMudhra certificate keys.12
The delay matters because this is not a cosmetic last-minute polish pass. Fedora's blocker process is designed to stop a release when a problem could make the operating system unsafe or significantly broken for users. The current list includes the eMudhra certificate issue, an LVM autoactivation failure after upgrading to Fedora 45, Plasma Discover installing outdated Fedora 44 RPMs, and a Stratis encrypted-pool boot failure.1
The eMudhra problem is a trust-store headache
The eMudhra incident concerns eight compromised intermediate certificate private keys. The incident site says the keys can be used to impersonate websites or services, and that the affected intermediates chain to roots trusted by major browser and operating-system programmes.3 That makes the problem broader than a single Fedora package: any software that continues trusting the affected certificate paths could potentially accept a fraudulent service.
The incident site says Firefox and Chrome blocked the certificates on 17 October, Microsoft platforms followed on 20 October, and Apple products acted on 22 October.3 It also warns that many other clients do not consume revocation information consistently, leaving software updates and trust-store changes as an important part of the fix.
Fedora's own blocker record, Bug 2556376, is marked as an accepted final blocker for Fedora 45. The report calls for an update to mitigate the current eMudhra issues, while its discussion points to the compromised intermediates and the need to remove affected trust paths.2 Fedora's blocker list currently marks the issue ON_QA, which means the fix is in testing rather than being a purely theoretical release concern.1
Four blockers, one release decision
The eMudhra issue is only one reason Fedora 45 has been held back. Fedora's final blocker list also records an LVM bug that can reject a LUKS-backed physical volume as too small after the upgrade, a Plasma Discover problem that can install outdated native packages from Fedora 44 repositories, and a Stratis failure that can prevent an encrypted pool from booting.1
That combination explains why the project is not treating the certificate problem in isolation. Fedora 45 is a major operating-system release, so shipping while several installation, upgrade and boot paths remain risky would simply move the testing burden on to users. The project has instead kept the release in the blocker process and set 3 November as the revised target reported by XDA Developers.4
A target date is not the same thing as a guarantee. Fedora's blocker list still includes fixes that need testing, and the release can move again if the remaining issues do not meet the project's criteria. The useful signal is therefore not just the date but whether the four accepted blockers leave the list and reach verified or otherwise resolved states.1
What Fedora users should do
Anyone waiting for Fedora 45 should treat the delay as a reason to stay on a supported existing installation rather than rush into unofficial images. Fedora's official Magazine material previously described Fedora 45 beta as available for testing, but the final release is a separate milestone and remains subject to the blocker process.5
Users who need to assess the eMudhra exposure should be careful about the distinction between browser revocation systems and independent certificate bundles. The incident site provides a checker and platform-specific mitigation guidance, but it also notes that applications using their own CA bundles may need separate updates.3 In practical terms, a browser appearing protected does not automatically prove that every application on the same machine has stopped trusting the compromised intermediates.
Our opinion
Holding Fedora 45 is the right call. A release delay is frustrating, especially when a new version is already being discussed and tested, but the blocker list describes failures in exactly the areas where a Linux distribution needs to be boring: certificate trust, upgrades, package delivery and booting. The eMudhra incident adds a genuine security dimension, while the other three blockers show that the release still has reliability work to do.
The best outcome is not a launch on 3 November at any cost. It is a release that reaches that date with the certificate mitigation and the remaining upgrade, package and boot fixes properly tested. Fedora's own blocker tracker is the source to watch as the date approaches; if the accepted blockers remain unresolved, another delay would be preferable to asking users to discover the failures in production.