Evidence · DiggingBeagle record
Pulse advisory: agent tokens redirect other host Proxmox connections
Project advisory for cross-connection host-agent registration and affected versions.
- Published
- Nov 13, 2026
- Source role
- primary disclosure
Evidence record
Project advisory for cross-connection host-agent registration and affected versions.
Claim-level citations (2)
- supportsA Pulse host-agent token could change credentials or destinations belonging to another monitored connection: The Pulse auto-registration handler accepted an agent token for one host but did not bind the request to the intended Proxmox VE or Backup Server connection. A token that identifies an allowed agent was mistakenly accepted as authority to replace a different connection's credential or address. The advisory describes overwriting and monitoring redirection, rather than theft of the previous credential: the old stored value was replaced. The 6.8.0 line tightened host/connection binding and made a fresh install grant necessary for reassignment.
Pulse GHSA-8cc7-g59j-5c4v, Impact, auto-register route and remediation
- supportsA Pulse host-agent token could change credentials or destinations belonging to another monitored connection: The impact presupposes a valid same-organization agent token and a host configuration within the affected versions. There is no evidence in the advisory of actual external customer exploitation. The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Primary disclosure: results, scope and limitations