VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

apache2: vulnerability history, versions and safety

apache2 is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 13 releases, from Jul 2014 to May 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
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 apache2 vulnerabilities

Vulert verdict on apache2 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 3 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 10 over 3 years · 0 in the last year i
  • Latest disclosure 30 May 2018 i
  • Highest CVSS n/a 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 apache2, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2015 2
  • 2016 1
  • 2017 5
  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for apache2

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Apache2 - Security Update N/A unrated 2.2.22-13+deb7u9 02 Jul 2017
Apache2 - Authorization Digest Header Value Placeholder Initialization Vulnerability N/A unrated 2.2.22-13+deb7u10 17 Jul 2017
Apache2 - Incorrect Parsing of Limit Directives in .htaccess Files N/A unrated 2.2.22-13+deb7u12 21 Sep 2017
Apache2 - Out of Bound Write and Replay Attack Vulnerabilities N/A unrated 2.2.22-13+deb7u13 30 May 2018
Apache2 - Proxy Header Remote Code Execution N/A unrated 2.2.22-13+deb7u7 20 Jul 2016

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 apache2

Is apache2 safe to use?

Vulert records 10 vulnerabilities for apache2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 apache2 have?

10 vulnerabilities are recorded for apache2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 apache2 vulnerabilities disclosed?

0 vulnerabilities were recorded for apache2 in the last 12 months, and the oldest entry in this database dates to 24 Jul 2014. 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 apache2 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 apache2 for upcoming vulnerabilities?

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