Case · DiggingBeagle record

A 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.

Public disclosure: Nov 13, 2026

Scope

A subordinate host agent already has a valid token for its own permitted monitoring instance.

UnratedAI role: AGAINST AIAssessment method

At a glance

Mechanism and trust boundary

  1. 01

    Starting condition

    A subordinate host agent already has a valid token for its own permitted monitoring instance.

    Boundary: precondition and attacker capability

  2. 02

    Trust boundary crossed or evaluated

    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.

    Boundary: mechanism

  3. 03

    Observed consequence

    Registration identity is accepted as authority over a different mutable host connection; the monitoring plane can then be redirected or disabled.

    Boundary: observed effect and limitations

Claims & evidence

CLM-NOV15-PULSEHOST-MECHThe 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.supported

Basis: reported finding

Link to claim
CLM-NOV15-PULSEHOST-SCOPEThe 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.supported

Basis: reported finding

Link to claim

Implications

Registration identity is accepted as authority over a different mutable host connection; the monitoring plane can then be redirected or disabled.

Controls and mitigations

  • Bind the registration proof to the original host:port and exact connection, and require an explicit fresh grant for transfers.
  • Audit connection-target changes from agent identities and compare real hypervisor telemetry to new destination addresses.

Unknowns and contradictions

  • 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.

Sources and citation

Material revision history

  1. Nov 15, 2026 · Canonical change recorded · new in release · revision 250