VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pacemaker: vulnerability history, versions and safety

pacemaker is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 23 releases, from Nov 2013 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded U17
i
1 with no fix published

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

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

Most recent disclosure 16 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pacemaker vulnerabilities

Vulert verdict on pacemaker i

Updated on 23 Oct 2026

Careful: one of the 17 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 17 vulnerabilities on record across 12 years, 1 in the last year.

What to do: Plan around the 1 vulnerability 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 17 over 12 years · 1 in the last year i
  • Latest disclosure 16 Jun 2026 i
  • Highest CVSS 8.6 i
  • With no published fix 1 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 pacemaker, 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 23 of 23 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2017 2
  • 2018 2
  • 2019 8
  • 2020 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pacemaker

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Overflow Vulnerability in Pacemaker Leading to Denial of Service 8.6 high No fix published 16 Jun 2026
Authorization Flaw in Pacemaker Allows Root Access via IPC Interface 7.8 high 1.1.15-3 10 Sep 2018
Local Privilege Escalation Vulnerability in Pacemaker (CVE-2018-16877) 7.8 high 2.0.1-3 18 Apr 2019
Use-After-Free Vulnerability in Pacemaker: Information Leak Risk 7.5 high 2.0.1-3 18 Apr 2019
Denial of Service Vulnerability in Pacemaker Remote 7.5 high 1.1.15~rc3-1 24 Mar 2017

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 pacemaker

Is pacemaker safe to use?

Vulert records 17 vulnerabilities for pacemaker in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does pacemaker have?

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

1 vulnerability was recorded for pacemaker in the last 12 months, and the oldest entry in this database dates to 23 Nov 2013. 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 pacemaker 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 pacemaker for upcoming vulnerabilities?

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