FreeBSD takes security very seriously and its developers are constantly working on making the operating system as secure as possible. This page will provide information about what to do in the event of a security vulnerability affecting your system

• Reporting FreeBSD security incidents

• Recent FreeBSD security vulnerabilities

• Understanding FreeBSD security advisories

• How to update your system

• Supported FreeBSD releases

• The FreeBSD support model

FreeBSD security issues specific to the base system should be reported via email to the FreeBSD Security Team or, if a higher level of confidentiality is required, via PGP encrypted email to the Security Officer Team using the Security Officer PGP key. Additional information can be found at the reporting FreeBSD security incidents page.

For every issue that gets reported, an internal tracking number is created, unless something is very obviously not a security issue. To determine whether or not a Security Advisory is warranted we use the following scheme:

• Is it a privilege escalation vulnerability?

• Is it a code injection vulnerability?

• Is it a memory disclosure or dataleak vulnerability?

  • From either the kernel

  • From a privileged process

  • From a process owned by another user?

• Is it a Denial of Service vulnerability?

  • Only when remotely exploitable, where remotely means that it comes from a different broadcast domain, so ARP and/or NDP based attacks do not qualify.

• Is it an unassisted jailbreak vulnerability?

• Is it a malfunction that could lead to generating insecure crypto keys, such as a PRNG bug?

For items that fall under these categories, a Security Advisory is very likely. Items that are not on this list are looked into individually and it will be determined then whether or not it will receive a Security Advisory or an Errata Notice.

Once it had been determined that a Security Advisory is warranted, either the submitter delivers a CVE number if he/she already requested one, or we use one from the FreeBSD pool available.

A full list of all security vulnerabilities affecting the base system can be found on this page.

A full list of all other errata affecting the base system can be found on this page.

Advisories affecting the base system are sent to the following mailing lists:

• [email protected]

• [email protected]

• [email protected]

The list of released advisories can be found on the FreeBSD Security Advisories page.

Advisories are always signed using the FreeBSD Security Officer PGP key and are archived, along with their associated patches, at the https://security.FreeBSD.org web server in the advisories and patches subdirectories.

The FreeBSD Security Officer provides security advisories for -STABLE Branches and the Security Branches. (Advisories are not issued for the -CURRENT Branch, which is primarily oriented towards FreeBSD developers.)

• The -STABLE branch tags have names like stable/14. The corresponding builds have names like FreeBSD 14.4-STABLE.

• Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like releng/14.4. The corresponding builds have names like FreeBSD 14.4-RELEASE-p4.

Issues affecting the FreeBSD Ports Collection are covered separately in the FreeBSD VuXML document.

Errata affecting the base system but not classified as security vulnerabilities are covered separately on the FreeBSD Errata Notices page.

For users that have previously installed a binary version of FreeBSD (e.g., 15.0 or 14.4), commands:

# freebsd-update fetch

# freebsd-update install

If that fails, follow the other instructions in the security advisory you care about.

Note that the above procedure is only for users who have previously installed a binary distribution. Those who have built from source will need to update their source tree to upgrade.

For more details, read how to apply security patches.

Each release is supported by the Security Officer for a limited time only.

The designation and expected lifetime of all currently supported branches and their respective releases are given below. The Expected EoL (end-of-life) column indicates the earliest date on which support for that branch or release will end. Please note that these dates may be pushed back if circumstances warrant it.

Older releases are not supported and users are strongly encouraged to upgrade to one of these supported releases:

In the run-up to a release, a number of -BETA and -RC releases may be published for testing purposes. These releases are only supported for a few weeks, as resources permit, and will not be listed as supported on this page. Users are strongly discouraged from running these releases on production systems.

Each minor release is only supported for three months after the next minor release within the same major version, or (for the final minor release) until support for the major version’s stable branch ends. From FreeBSD 15 onward, each stable branch is explicitly supported for 4 years from its dot-zero release. Support for the stable branch of FreeBSD 14 ends on November 30, 2028.

This model’s rationale is detailed in the official announcements of the 4-year support period for stable branches, sent in July 2024, and the switch to a branch-based support model, sent in February 2015.