Compare lighttpd
Head-to-head on security track record — known CVEs, active exploitation and support status:
Summary iPlain-English security verdict for lighttpd, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
lighttpd currently scores 85/100 — good. No tracked vulnerabilities are currently known to be exploited in the wild. It's largely safe; apply minor updates as they appear.
Disclosure trend iNew CVEs published for lighttpd 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-2025-12642 CRITICAL CWE-444 EPSS 0% → see advisoryGet alerted about lighttpd
Be emailed the moment lighttpd 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 lighttpd — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is lighttpd safe and patched?
lighttpd currently scores 85/100 — good. No tracked vulnerabilities are currently known to be exploited in the wild. It's largely safe; apply minor updates as they appear.
What should I do about lighttpd now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against lighttpd'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 lighttpd's official advisory before you patch or upgrade — lighttpd official site ↗