Red Hat announced the general availability of Red Hat Enterprise Linux 10.3 and 9.9 on 11 November 2026, two days after previewing both releases at KubeCon + CloudNativeCon North America. The headline is not a version bump: it is proof that the system running in production is the system you deployed, and AI help that works with real diagnostics instead of guesses.
Sealed images: the OS that refuses tampered content
Sealed images, now generally available in RHEL 10.3 for image mode, sign and verify the whole OS with your own secure boot keys. The chain runs from firmware and bootloader through the kernel to the root filesystem, and the root filesystem stays read-only. Tampered content is refused by the kernel at read time rather than served.
For operators, this changes the failure mode. A compromised file no longer sits quietly until the next audit finds it; the system refuses to use it. If you deploy with bootc image mode, the image you tested is the image that runs, on every node, with no drift between them. Image mode treats the OS as a container image you build, test, and roll back as one unit; sealed images add the missing piece, cryptographic proof that nobody swapped a file between build and boot.
An MCP server graduates, and AI diagnostics get real data
The second headline is the Model Context Protocol server for RHEL moving from Developer Preview to general availability. Packaged as an RPM in the extensions repository, it connects AI assistants to live RHEL system data, and it works with goose, Red Hat's open source AI command-line agent.
What makes this more than a chatbot bolted onto a server is the data behind it. The MCP server integrates historical Performance Co-Pilot data, so an assistant can look at past performance events instead of only the current snapshot. Intermittent issues, the ones that vanish before you can SSH in, are exactly the cases where a history-aware diagnostic earns its keep. Access is governed by default, so treat the MCP server like any new privileged service: enable it in a lab first, scope what it can read, and only then point it at production.
Self-managed AI help for disconnected rooms
The command-line assistant, the natural-language helper for the terminal, can now run self-managed with customer-hosted inference, in Developer Preview. Regulated and air-gapped environments can keep the model and the operational context inside their own perimeter instead of sending questions to a hosted service. That is a small line in the announcement with a large audience: plenty of RHEL estates cannot send anything to a cloud AI service, and until now their choice was hosted AI or no AI.
Toolchains, post-quantum crypto, and the upgrade path
Under the hood, RHEL 10.3 stays on the 6.12 kernel and ships GCC 16, LLVM 22, Go 1.27, .NET 11, Node.js 26 LTS, PHP 8.4, and Rust 1.97. Post-quantum cryptography support lands in the Go toolchain, aimed at CNSA 2.0 compliance and the harvest-now-decrypt-later threat.
The upgrade story is the part most readers will actually use. Red Hat validated in-place upgrade paths with Leapp from RHEL 9.9 to 10.3 and from RHEL 8.10 to 9.9. If you run 9.x, the supported route to 10 is now 9.9 first, then Leapp to 10.3. The pre-flight discipline is the same one we laid out in our openSUSE Leap 16.1 upgrade playbook: back up before you start, and test the upgrade on a disposable clone before touching a production box. Fedora users will recognise the drill, since Fedora is RHEL's upstream, and our Fedora 45 upgrade playbook covers the same snapshot-first habit.
What to do this week
- If you run RHEL 9, plan the hop to 9.9, then Leapp to 10.3. Do not skip the intermediate step.
- If you use image mode, try a sealed image build in a lab and verify the boot chain rejects a tampered file.
- If you want AI diagnostics, install the MCP server next to goose on a non-production host and scope its access before it meets real data.
- If you only want to look, Red Hat offers a 60-day trial of RHEL 10.3, and a Timeshift snapshot of your test box makes rolling back trivial.
RHEL 10.3 is not a flashy release. It is a foundation release, and that is the point. Sealed images make the OS prove itself, the MCP server makes AI troubleshooting use real evidence, and the upgrade path is mapped.
