security.freesense.org: every FreeBSD advisory, and what it means for FreeSense
A new site lists every FreeBSD security advisory since 2025 with a decision for FreeSense 1.0, 1.1 and 1.2, and FreeSense's own bugs and issues next to them.
FreeSense is built on FreeBSD, so FreeBSD's security advisories matter to us. The new security site lists every one of them since 2025 and says what it means for each FreeSense version.
Open, fixed or not relevant
Every advisory has a status for FreeSense 1.0, 1.1 and 1.2:
- Open: it applies to code we build, and the fix is not in the FreeBSD snapshot that version builds from yet.
- Fixed: FreeBSD corrected it before that snapshot.
- Not relevant: it is about code FreeSense does not build or ship. The page names the evidence from our build configuration.
Each advisory has its own page with the CVE IDs, the affected FreeBSD releases, the correction dates and any workaround, and links to the original FreeBSD advisory. FreeSense 1.0 is frozen, so an advisory that is open on 1.0 stays open there; the fix is to update to 1.1.
Bugs and issues, too
FreeSense's own bugs and issues from GitHub are listed in the same place, each with a badge: Bug, Security report or Issue. Open and closed ones are both shown.
An honest note on the statuses
Most statuses are decided automatically, by comparing the date FreeBSD corrected an advisory with the date of the FreeBSD source each version is pinned to, and they are marked auto until a maintainer reviews them. They do not tell you whether your own system is exposed: a bug in a kernel module only matters if the module is loaded. FreeBSD advisories carry no severity score, so we do not invent one. The triage page explains the method and its limits.
For now the site covers the FreeBSD base system and FreeSense's GitHub issues. Advisories for ports and the optional packages are planned next.
Report a vulnerability
Found a security problem in FreeSense? Please report it privately so we can fix it before it is public.