The FreeBSD Project released FreeBSD 14.5-RELEASE on September 8, 2026, the sixth release of the stable/14 branch. The Release Engineering team puts it plainly in the announcement: because it arrives late in a stable branch that is now considered legacy, there are few new features and the effort has gone into maintenance. Changes since 14.4 are mostly bug fixes, driver updates and new versions of the externally maintained software that ships in the base system.
That makes the picture fairly simple. If you have machines on FreeBSD 14, there is now a maintenance release to move them to. If you are building a server from scratch, the project’s recommendation is to install FreeBSD 15.1, which came out in June and is the current production release.
The dates that matter
| Version | Announced support status |
|---|---|
| FreeBSD 14.4-RELEASE | End of life on December 31, 2026 |
| FreeBSD 14.5-RELEASE | Supported until June 30, 2027 |
FreeBSD 14 series (stable/14) |
Supported until November 30, 2028 |
| New installations | The project recommends 15.1 |
Two different things are easy to mix up here. One is the end of support for a point release (14.5 loses it on June 30, 2027) and the other is the end of the whole branch, which for 14 runs until the end of November 2028. There is room for another 14.x or two in between, and above all there is time to plan the jump to the next generation without rushing.
FreeBSD’s support model works like this: each minor release is supported for three months after the next one within the same major branch, and the branch as a whole has its own date. From 15 onward, each stable branch is also supported for four years from its .0 release. The current figures are on the FreeBSD page.
Who 14.5 is for, and who it isn’t
A server already running FreeBSD 14 has plenty of reasons to stay on the branch: kernel modules built against it, specific drivers, appliances, internal procedures that have already been tested. In that case moving to 14.5 is the conservative route, because you change the point release without changing the operating system generation at the same time. Changing both at once is exactly what you don’t want to be doing on a Tuesday afternoon in production.
A new installation has none of those ties. Starting on 14.5 today means adopting a point release with less than a year of support left, which is why the project steers new deployments toward 15.1. With 15 you also get what we covered when 15.0 came out: a base system installable with pkg, OpenZFS 2.4, OpenSSH 10 with post-quantum cryptography and native inotify.
And anyone still on 14.4 has a date to write down: December 31, 2026. After that, no more security patches.
What’s inside
The release notes are long for a specific reason: 14.5 rolls up every security advisory issued for the branch since March, including several we have covered here, such as the root privilege escalation via execve(), the remote code execution in RPCSEC_GSS, the dhclient, pf, ptrace and setcred bugs, the KTLS issues and two batches of OpenSSL fixes. Installing from the new image saves applying them one by one.
Third-party software moves to LLVM 21.1.8, OpenSSL 3.0.21, libarchive 3.8.7, libpcap 1.10.6, ncurses 6.6, less 704, file 5.47, Expat 2.8.1 and ldns 1.9.2. The default linker for clang is now ld.lld, and ipfw ships a fallback ipfw15 binary so firewall rules still load if you boot a 15 kernel partway through an upgrade.
There are small details someone has been waiting for. pwd switches its default from -P to -L to match POSIX, the sh history grows from 100 to 128 entries for the same reason, daemon gains a -m option to set the output file mode, rc.firewall can read addresses and subnets from files on disk, and lpd once again honours the port set in /etc/printcap, which had been broken since IPv6 support was added in 2000. On the tape side, mt and libmt now recognise LTO-10 and LTO-10P.
Images for almost everything
14.5 is available for amd64, i386, aarch64, armv7, powerpc, powerpcspe, powerpc64, powerpc64le and riscv64, with dedicated SD card images for Raspberry Pi 3 and 4, PINE64, PINEBOOK, ROCK64 and ROCKPRO64. On amd64 the usual set is there: dvd1 with documentation, debugging sets and a handful of packages to get a desktop up; disc1 with just the base system; bootonly and mini-memstick to boot and install over the network; and memstick for a USB install, all of them with a livefs rescue mode.
For virtualisation there are pre-installed images in QCOW2, VHD, VMDK and RAW, with BASIC-CLOUDINIT variants on amd64 and aarch64. In the public cloud there are AMIs for Amazon EC2 (UFS and ZFS, in base, builder, cloud-init and small configurations), images for Google Compute Engine and, according to the announcement, the Azure Marketplace ones are on their way. There are OCI images for amd64, i386, aarch64 and riscv64 too, which package a FreeBSD userland but still run on the host kernel, so don’t mistake that for running FreeBSD inside a Linux container.
Two warnings the project repeats and which bear repeating. When writing an image with dd, double-check the device in of=, because a slip overwrites the wrong disk. And the ARM images ship with a freebsd user whose password is freebsd and a root password of root, meant for SSH access on systems without a console. Change both as soon as you log in.
How to upgrade
On a binary install, freebsd-update is enough:
# freebsd-update fetch
# freebsd-update installBefore touching a production machine, read the release notes, the hardware compatibility list and the errata, which the project publishes separately because real compatibility depends on each server. SHA-256 and SHA-512 sums and PGP-signed checksum files are on the FreeBSD website to verify the images before use.
Sources: FreeBSD 14.5-RELEASE announcement and release notes from the FreeBSD Project; FreeBSD 14.5 ya está disponible, pero los nuevos servidores deberían usar 15.1, at Administración de Sistemas.