How we triage.

The three statuses

• Open The advisory applies to code FreeSense builds, and the fix is not in our FreeBSD snapshot yet.
• Fixed FreeBSD corrected it before the snapshot that FreeSense builds from.
• Not relevant The advisory is about code FreeSense does not build or ship. The page names the evidence.

Automatic first, then reviewed

The status starts from two facts. First, the correction date in the advisory compared with the date of the FreeBSD source pin of each FreeSense version. FreeBSD fixes land on the development branch first, so the earliest correction date is a good, but not perfect, guide to when the fix reached the snapshot. Second, a short list of components that the FreeSense build configuration leaves out (bhyve, blocklistd, lpr, lpd, talkd, comsat, sendmail, rdist).

These automatic results are marked auto. A maintainer can review an advisory and write a decision with a reason and evidence. A reviewed decision replaces the automatic one and loses the auto mark.

What the automatic status cannot tell you

• Whether your FreeSense is exposed in practice. A bug in an optional kernel module only matters if the module is loaded.
• Whether an advisory about older FreeBSD releases applies to the development branch that FreeSense follows.
• Severity. FreeBSD advisories do not carry a CVSS score, so we do not invent one.

Open means "check this", not "you are being attacked". Read the advisory and its workaround.

Versions and pins

Each version builds from a pinned FreeBSD snapshot. On the maintained versions the pin normally changes about every 14 days. FreeSense 1.0 is frozen: it stays on its last pin and gets no further fixes, so an advisory that is open on 1.0 stays open. The fix is to update to 1.1.

• FreeSense 1.0 1.0.7: FreeBSD 16 (main snapshot), pinned 2026-08-03 (e004ff15)
• FreeSense 1.1 1.1.9: FreeBSD 16 (main snapshot), pinned 2026-10-04 (a52c50b4)
• FreeSense 1.2 1.2.0-DEVELOPMENT: FreeBSD 16 (main snapshot), pinned 2026-10-04 (a52c50b4)

Bugs and issues

FreeSense's own bugs and issues come from the GitHub issues of the FreeSense repositories and are listed next to the advisories, each marked with a badge: Bug, Security report (an issue labelledbug/cve report) or Issue. An open issue is Open, a closed one is Closed, and one closed as not planned is Not planned. Issues are not tied to a FreeSense version, so choosing a version hides them.

Scope today

84 FreeBSD base system advisories from 2025 to now. Advisories for software installed from ports (the FreeBSD VuXML database) and for the FreeSense optional packages are planned next.