VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

lighttpd: vulnerability history, versions and safety

lighttpd is a package in the Debian ecosystem. Vulert records 64 vulnerabilities for it across 2 releases, from Apr 2007 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
64 vulnerabilities recorded U64
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lighttpd vulnerabilities

Vulert verdict on lighttpd i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 24 Sep 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 64 vulnerabilities on record across 18 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 64 over 18 years · 0 in the last year i
  • Latest disclosure 24 Sep 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for lighttpd, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.4.59-1 U5 Yes Details →
1.4.59-1+deb11u1 U4 Yes Details →

Newest 2 of 2 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 16
  • 2008 14
  • 2010 2
  • 2011 2
  • 2012 2
  • 2013 8
  • 2014 4
  • 2015 2
  • 2018 2
  • 2019 2
  • 2022 7
  • 2024 2
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 64 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for lighttpd

The 5 most severe of 64 vulnerabilities recorded for this package

Search all 64 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Signed Integer Overflow in Lighttpd - CVE-2019-11072 9.8 critical 1.4.53-4 10 Apr 2019
Critical SQL Injection Vulnerability in Lighttpd Package 9.8 critical 1.4.33-1+nmu3 14 Mar 2014
Arbitrary Log Injection in mod_auth of lighttpd 7.5 high 1.4.37-1 09 Jun 2015
Denial of Service Vulnerability in Lighttpd Package: CVE-2022-30780 7.5 high 1.4.59-1 11 Jun 2022
Path Traversal Vulnerability in Lighttpd Package - CVE-2018-19052 7.5 high 1.4.52-1 07 Nov 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About lighttpd

Is lighttpd safe to use?

Vulert records 64 vulnerabilities for lighttpd in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 64 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does lighttpd have?

64 vulnerabilities are recorded for lighttpd in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 64 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new lighttpd vulnerabilities disclosed?

0 vulnerabilities were recorded for lighttpd in the last 12 months, and the oldest entry in this database dates to 18 Apr 2007. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of lighttpd are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor lighttpd for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the lighttpd version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.