LibreNMS ↗
Summary iPlain-English security verdict for LibreNMS, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
LibreNMS currently scores 39/100 — high risk. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade soon — serious vulnerabilities are open and a fix usually exists.
Disclosure trend iNew CVEs published for LibreNMS each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2024-51092 CRITICAL OS command injection EPSS 7% → fixed in 24.10.0 CVE-2026-86426 CRITICAL Improper authentication EPSS 1% → fixed in 26.8.0Get alerted about LibreNMS
Be emailed the moment LibreNMS gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for LibreNMS — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is LibreNMS safe and patched?
LibreNMS currently scores 39/100 — high risk. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade soon — serious vulnerabilities are open and a fix usually exists.
What should I do about LibreNMS now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against LibreNMS's official advisory.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against LibreNMS's official advisory before you patch or upgrade — LibreNMS official site ↗