← Back to home
Comparison · Infra & APIs

Pacemaker vs Greenbone Vulnerability Manager

A side-by-side editorial comparison of Pacemaker and Greenbone Vulnerability Manager — release velocity, themes, recent moves, and the top alternatives to consider.

Pacemaker vs Greenbone Vulnerability Manager: at a glance

FeaturePacemakerGreenbone Vulnerability Manager
SectorInfra & APIsInfra & APIs
Velocity score6.36.3
Sparks · 30d11
Top themeshigh availability, cluster security, tls authentication, dual branch releasesvulnerability management, web application scanning, gmp protocol, report modeling
Last editorial update3h ago3h ago
WebsiteVisit →Visit →

What is Pacemaker?

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.

Read the full Pacemaker trajectory →

What is Greenbone Vulnerability Manager?

Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.

gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.

Read the full Greenbone Vulnerability Manager trajectory →

Pacemaker vs Greenbone Vulnerability Manager: editorial side-by-side

P
Pacemaker
INFRA · APIS
6.3

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

◆ Current state

Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.

◆ Where it's heading

The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.

◆ Prediction

Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.

G6.3

Greenbone's scanner daemon is growing a web-application scanning class beside its network roots.

◆ Current state

gvmd releases every week or two, and the changelog splits cleanly in three: a sustained build-out of web application scanning, a rewrite of how reports are modeled and exported, and a long tail of memory-management fixes in the C core. Recent versions added web application scanner preferences, scanner verification, and a Web Application VT subtype with a database migration. The report work moved from ad-hoc XML toward a structured report model addressable through new GMP commands.

◆ Where it's heading

Greenbone is widening what gvmd can orchestrate. Network and container scanning were the existing surface; web application scanning is being brought to parity, with its own VT class, preferences, validation, and verification path. In parallel the GMP protocol is gaining first-class report retrieval commands, which makes report data consumable by tooling rather than only renderable. The bug-fix stream is dominated by frees and cleanup in long-lived report paths, the signature of a codebase under memory pressure at scale.

◆ Prediction

Web Application VTs now have a subtype, a migration, and scanner verification, but the audit and scan report commands were added separately; expect the report model work to fold web application results into the same structured retrieval path rather than leaving a parallel one.

Alternatives to Pacemaker and Greenbone Vulnerability Manager

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Pacemaker or Greenbone Vulnerability Manager.

See all Pacemaker alternatives → · See all Greenbone Vulnerability Manager alternatives →

Recent activity from Pacemaker and Greenbone Vulnerability Manager

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5d agoGreenbone Vulnerability Manageropenvasd library bumped to 23.9
  2. 5d agoGreenbone Vulnerability ManagerGMP gains a get_audit_report_hosts command
  3. 10d agoGreenbone Vulnerability ManagerWeb Application VTs become a first-class scan type
  4. 11d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  5. 18d agoGreenbone Vulnerability ManagerStructured report model and the get_scan_report command
  6. 19d agoGreenbone Vulnerability ManagerPer-object asset permissions and report-script trust checks
  7. 24d agoGreenbone Vulnerability ManagerAggregate grouping and family-name fixes
  8. 28d agoPacemaker3.0.2: PSK auth for remote CIB operations
  9. 28d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote
  10. 28d agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  11. 1mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  12. 1mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport

Frequently asked questions

What is the difference between Pacemaker and Greenbone Vulnerability Manager?

They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker and Greenbone Vulnerability Manager are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Pacemaker better than Greenbone Vulnerability Manager?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker and Greenbone Vulnerability Manager are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Pacemaker?

Top Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.

What are the best alternatives to Greenbone Vulnerability Manager?

Top Greenbone Vulnerability Manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Greenbone Vulnerability Manager alternatives" section above for the current picks, or visit /alternatives/greenbone-gvmd for the full list with editorial commentary on each.