VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

icinga2: vulnerability history, versions and safety

icinga2 is a package in the Debian ecosystem. Vulert records 32 vulnerabilities for it across 42 releases, from Nov 2017 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
32 vulnerabilities recorded U32
i
7 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 10 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all icinga2 vulnerabilities

Vulert verdict on icinga2 i

Updated on 23 Oct 2026

Careful: 7 of the 32 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 32 vulnerabilities on record across 8 years, 3 in the last year.

What to do: Plan around the 7 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 32 over 8 years · 3 in the last year i
  • Latest disclosure 10 Aug 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 7 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 icinga2, 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 42 of 42 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2018 10
  • 2020 4
  • 2021 6
  • 2024 3
  • 2025 4
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for icinga2

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Certificate Renewal Bypass in Icinga 2: CVE-2020-29663 9.1 critical 2.12.3-1 15 Dec 2020
Privilege Escalation Vulnerability in Icinga2 Monitoring System 8.8 high 2.12.3-1+deb11u1 15 Jul 2021
Credential Exposure Vulnerability in Icinga2 Monitoring System 8.8 high 2.12.3-1+deb11u1 15 Jul 2021
CVE-2018-6535: Password Disclosure Vulnerability in Icinga 2.x 8.1 high 2.8.4-1 27 Feb 2018
Icinga2 Vulnerability CVE-2020-14004: Arbitrary File Permissions via Symlink 7.8 high 2.11.5-1 12 Jun 2020

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 icinga2

Is icinga2 safe to use?

Vulert records 32 vulnerabilities for icinga2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 32 not yet rated. 7 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does icinga2 have?

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

3 vulnerabilities were recorded for icinga2 in the last 12 months, and the oldest entry in this database dates to 24 Nov 2017. 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 icinga2 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 icinga2 for upcoming vulnerabilities?

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