# Security tab: let me mark a CVE as not applicable & add a note

**Project:** Panel | **Votes:** 0
**URL:** https://roadmap.ploi.io/projects/3-panel-requests/items/1657-security-tab-let-me-mark-a-cve-as-not-applicable-add-a-note

---

The new Security tab is very useful :-). But right now every flagged CVE sits there as an open item until Debian ships a package update, even when the vulnerability cannot apply to the server at all. I would like a way to triage findings rather than just wait on them.

Example from this week. CVE-2026-123158 (OpenSSH password bypass) was flagged on my server as actively exploited with no fix released. The vulnerable condition is sshd built against musl libc without PAM, which is the Alpine configuration. A Debian or Ubuntu Ploi server uses glibc with PAM, and password authentication is off by default, so the finding is noise for every standard Ploi install. Yet it shows as a red “wait for the fix” item with no way to say so.

What I am asking for:
1. Mark as not applicable, per CVE and per server, with a short free text note (for example “Debian uses glibc and PAM, password auth is off, verified with sshd -T”). Dismissed items drop out of the main list and the server’s risk count, with a “show dismissed” toggle so they are still auditable.
2. Apply to all my servers as an option when dismissing, for findings that cannot apply to any standard Ploi setup.
3. Reopen automatically if the installed package version changes or the CVE details are updated, so a dismissal never silently hides a finding that has become real.
4. Ploi level pre flagging where the platform already knows the answer. If a CVE only affects a build configuration Ploi never ships (musl, no PAM, a desktop component, a kernel module Ploi does not install), label it “not applicable to standard Ploi setups” out of the box, with the reasoning shown. That would save every customer doing the same investigation.
5. Notes on open items too. Even for a finding that does apply, I want to record what I checked and what mitigation is in place (firewall rule, package removed, config change) so that the tab becomes a record of my triage rather than only a feed of Debian’s tracker.
